xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] xen: don't use PCI BIOS service for configuration space accesses
Date: Fri, 13 Apr 2012 16:25:13 +0100	[thread overview]
Message-ID: <4F884559.5000800@citrix.com> (raw)
In-Reply-To: <4F885120020000780007DD18@nat28.tlf.novell.com>

On 13/04/12 15:15, Jan Beulich wrote:
>>>> On 13.04.12 at 14:55, David Vrabel <david.vrabel@citrix.com> 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.
> 
> How is that? When I look at pci_arch_init(), I see pci_direct_probe()
> being called first.

Hmm. Direct /is/ preferred over BIOS.  But the BIOS is initialized even
if direct is eventually used and it's the init of the BIOS that dies.

I'll fixup the description to make this clearer.

David

  reply	other threads:[~2012-04-13 15:25 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 [this message]
2012-04-16 15:10     ` Konrad Rzeszutek Wilk
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=4F884559.5000800@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=konrad.wilk@oracle.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).