WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

FW: [Xen-users] Re: [Xen-devel] Xen - Guest memory allocation

To: xen developers community <xen-devel@xxxxxxxxxxxxxxxxxxx>, xen users community <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: FW: [Xen-users] Re: [Xen-devel] Xen - Guest memory allocation
From: dinesh chandrasekaran <dinesh_chan8@xxxxxxxxxxx>
Date: Mon, 23 Jun 2008 20:54:35 +0530
Delivery-date: Mon, 23 Jun 2008 08:25:03 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

       Xen, during boot up prints the following,

__  __            _____  _____                    _        _     _     
 \ \/ /___ _ __   |___ / |___ /    _   _ _ __  ___| |_ __ _| |__ | | ___
  \  // _ \ '_ \    |_ \   |_ \ __| | | | '_ \/ __| __/ _` | '_ \| |/ _ \
  /  \  __/ | | |  ___) | ___) |__| |_| | | | \__ \ || (_| | |_) | |  __/
 /_/\_\___|_| |_| |____(_)____/    \__,_|_| |_|___/\__\__,_|_.__/|_|\___|
                                                                        
(XEN) Xen version 3.3-unstable (reddy@(none)) (gcc version 4.1.1 (Gentoo 4.1.1-r3)) Sat May 31 00:05:56 Local time zone must be set--see zic manual page 2008
(XEN) Latest ChangeSet: Fri May 30 19:31:18 2008 +0100 17760:6e688d5a936b
(XEN) Command line:
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 2 seconds
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) pci_base =  df000000 : pci_2 = 0
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 0000000000094400 (usable)
(XEN)  0000000000094400 - 00000000000a0000 (reserved)
(XEN)  00000000000c2000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000cfe90000 (usable)
(XEN)  00000000cfe90000 - 00000000cfea3000 (ACPI data)
(XEN)  00000000cfea3000 - 00000000cff00000 (ACPI NVS)
(XEN)  00000000cff00000 - 00000000d0000000 (reserved)
(XEN)  00000000e0000000 - 00000000f0000000 (reserved)
(XEN)  00000000fec00000 - 00000000fec00400 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000fff80000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000230000000 (usable)
(XEN)  00000000df000000 - 00000000df0fffff (PCI_usable)             <this is the pci_device's BAR1 value>

but after DomO comes up, the config space dump of the pci_device obtained through,

lspci -xxxx <pci_device>

shows me a different BAR1 value.

Could someone tell me what could be the cause?

Thanks,
Dinesh C

> Date: Fri, 20 Jun 2008 18:03:20 +0100
> From: gm281@xxxxxxxxx
> To: dinesh_chan8@xxxxxxxxxxx
> Subject: Re: [Xen-users] Re: [Xen-devel] Xen - Guest memory allocation
> CC: xen-devel@xxxxxxxxxxxxxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
>
> >> Why do you want to restrict DomU to use frames from certain range
> >> only? What's the logic behind that?
> >
> > Im trying to allocate memory for domUs from memory behind a PCI device. The
> > machine_addr_start is obtained by probing the device (as I know the vendor
> > and device info) during xen boot-up.
>
> That's what I was suspecting. I think you should give PCI passthrough
> a go first.
> PCI passthrough allows a PCI device to be hidden away from Dom0 and
> exported to a DomU. You achieve the first by passing
> pciback.hide=(XX:XX.X) option to Dom0 kernel and adding pci = [
> 'XX:XX.X′ ] to DomU config file. You'll also need
> CONFIG_XEN_PCIDEV_FRONTEND=y and CONFIG_XEN_PCIDEV_BACKEND=y in your
> DomU and Dom0 kernel configs.
>
> Hope this helps
> Gr(z)egor(z)


CoolHotmail : Your crazy personality deserves a unique email identity like yourname@xxxxxxxxxxxx Choose from this and hundreds other unique email ids now Try it!


Placements ? No Problem. Register Here! Try it!


Skydrive - Get 5GB online space for FREE!. Store and share music, photos and documents online with ease. Try it now!

Attachment: ATT00001
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel