From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"keir.fraser@eu.citrix.com" <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH 4 of 5] libxl: Add support for passing in the machine's E820 for PCI passthrough
Date: Fri, 8 Apr 2011 10:34:52 -0400 [thread overview]
Message-ID: <20110408143452.GA9971@dumpdata.com> (raw)
In-Reply-To: <20110408142536.GL30961@whitby.uk.xensource.com>
On Fri, Apr 08, 2011 at 03:25:36PM +0100, Tim Deegan wrote:
> At 15:17 +0100 on 08 Apr (1302275848), Ian Campbell wrote:
> > > That's a _horrible_ config syntax.
> >
> > fair enough. I thought it nicely represented the "has an empty PCI bus"
> > myself...
>
> Sure, but it's really not obvious that that means "has a memory layout
> that matches the host on which it was last booted".
>
> > > We should either do this for all
> > > guests or give it its own option (which can default to 1 for guests with
> > > non-empty passthrough lists if you like).
> >
> > Ack, if it's an option it should definitely default to on for non-empty
> > pci passthrough lists. I think we can probably get away with default on
> > always though and allow it to be explicitly disabled. That's really just
> > a case of trying on a few PV OSes and seeing how much they barf...
>
> Agreed. My guess is there won't be any trouble.
Whoa. I just booted an SLES11 32 bit and it booted so nicely :-)
(2.6.27)
Time to try out some RHEL guests.
next prev parent reply other threads:[~2011-04-08 14:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 20:25 [PATCH 0 of 5] Patches for PCI passthrough with modified E820 Konrad Rzeszutek Wilk
2011-04-07 20:25 ` [PATCH 1 of 5] tools: Add xc_domain_set_memory_map and xc_get_machine_memory_map calls Konrad Rzeszutek Wilk
2011-04-08 8:18 ` Ian Campbell
2011-04-08 13:19 ` Konrad Rzeszutek Wilk
2011-04-07 20:25 ` [PATCH 2 of 5] x86: make the pv-only e820 array be dynamic Konrad Rzeszutek Wilk
2011-04-08 8:22 ` Ian Campbell
2011-04-08 13:21 ` Konrad Rzeszutek Wilk
2011-04-07 20:25 ` [PATCH 3 of 5] x86: adjust the size of the e820 for pv guest to " Konrad Rzeszutek Wilk
2011-04-07 20:25 ` [PATCH 4 of 5] libxl: Add support for passing in the machine's E820 for PCI passthrough Konrad Rzeszutek Wilk
2011-04-08 8:36 ` Ian Campbell
2011-04-08 10:56 ` Ian Jackson
2011-04-08 13:35 ` Konrad Rzeszutek Wilk
2011-04-08 13:55 ` Ian Campbell
2011-04-08 14:09 ` Tim Deegan
2011-04-08 14:17 ` Ian Campbell
2011-04-08 14:25 ` Tim Deegan
2011-04-08 14:33 ` Ian Campbell
2011-04-08 15:00 ` Konrad Rzeszutek Wilk
2011-04-08 14:34 ` Konrad Rzeszutek Wilk [this message]
2011-04-08 14:42 ` Ian Campbell
2011-04-08 14:54 ` Konrad Rzeszutek Wilk
2011-04-08 16:01 ` Ian Jackson
2011-04-08 13:33 ` Konrad Rzeszutek Wilk
2011-04-08 14:00 ` Ian Campbell
2011-04-07 20:25 ` [PATCH 5 of 5] libxl: Convert E820_UNUSABLE and E820_RAM to E820_UNUSABLE as appropriate Konrad Rzeszutek Wilk
2011-04-08 8:42 ` [PATCH 0 of 5] Patches for PCI passthrough with modified E820 Ian Campbell
2011-04-08 13:24 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110408143452.GA9971@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Tim.Deegan@citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).