From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] xen: don't use PCI BIOS service for configuration space accesses
Date: Mon, 16 Apr 2012 11:10:45 -0400 [thread overview]
Message-ID: <20120416151045.GH1903@phenom.dumpdata.com> (raw)
In-Reply-To: <4F88222F.7050703@citrix.com>
On Fri, Apr 13, 2012 at 01:55:11PM +0100, David Vrabel wrote:
> On 13/04/12 13:29, Jan Beulich wrote:
> >>>> On 13.04.12 at 14:08, David Vrabel <david.vrabel@citrix.com> wrote:
> >> From: David Vrabel <david.vrabel@citrix.com>
> >>
> >> The accessing PCI configuration space with the PCI BIOS service does
> >> not work in PV guests.
> >>
> >> This fixes boot on systems without MMCONFIG or where the BIOS hasn't
> >> marked the MMCONFIG region as reserved in the e820 map.
> >
> > ... and where "direct" access doesn't work either? Are there really
> > machines where Xen works on but this doesn't work? (Or, in case
> > this is disabled in your config, is it really useful to have
> > CONFIG_PCI_DIRECT disabled?)
>
> If you have CONFIG_PCI_GOANY (the default) BIOS is preferred over
> direct. So this change makes it skip BIOS and fall back to direct.
>
> On the system I had saw the problem, the first call into the BIOS
> service would hang the system.
>
> > That's just a comment on the description, the patch itself is fine
> > nevertheless (but should probably be sent to the x86 and/or PCI
> > maintainers).
>
> I was expecting Konrad to pick it up and forward it to the relevant
> maintainer as appropriate. Konrad, would you prefer if I sent to direct?
You can send it to me. But I think it makes sense to stick
this in arch/x86/pci/xen.c - if it is not to late in teh bootup cycle?
>
> >> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> >
> > Acked-by: Jan Beulich <jbeulich@suse.com>
> >
> >> Cc: stable@kernel.org
> >> ---
> >> arch/x86/xen/enlighten.c | 5 ++++-
> >> 1 files changed, 4 insertions(+), 1 deletions(-)
> >>
> >> diff --git a/arch/x86/xen/enlighten.c b/arch/x86/xen/enlighten.c
> >> index b132ade..dbb5bb7 100644
> >> --- a/arch/x86/xen/enlighten.c
> >> +++ b/arch/x86/xen/enlighten.c
> >> @@ -63,6 +63,7 @@
> >> #include <asm/stackprotector.h>
> >> #include <asm/hypervisor.h>
> >> #include <asm/mwait.h>
> >> +#include <asm/pci_x86.h>
> >>
> >> #ifdef CONFIG_ACPI
> >> #include <linux/acpi.h>
> >> @@ -1365,7 +1366,9 @@ asmlinkage void __init xen_start_kernel(void)
> >> /* Make sure ACS will be enabled */
> >> pci_request_acs();
> >> }
> >> -
> >> +
> >> + /* PCI BIOS service won't work from a PV guest. */
> >> + pci_probe &= ~PCI_PROBE_BIOS;
> >>
> >> xen_raw_console_write("about to get started...\n");
> >>
> >> --
> >> 1.7.2.5
> >>
> >>
> >> _______________________________________________
> >> Xen-devel mailing list
> >> Xen-devel@lists.xen.org
> >> http://lists.xen.org/xen-devel
> >
> >
> >
next prev parent reply other threads:[~2012-04-16 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 12:08 [PATCH] xen: don't use PCI BIOS service for configuration space accesses David Vrabel
2012-04-13 12:29 ` Jan Beulich
2012-04-13 12:55 ` David Vrabel
2012-04-13 14:15 ` Jan Beulich
2012-04-13 15:25 ` David Vrabel
2012-04-16 15:10 ` Konrad Rzeszutek Wilk [this message]
2012-04-16 15:40 ` David Vrabel
2012-04-16 16:33 ` 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=20120416151045.GH1903@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=david.vrabel@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).