From: Arjan van de Ven <arjan@linux.intel.com>
To: Brice Goglin <brice@myri.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] PCI extended conf space when MMCONFIG disabled because of e820
Date: Wed, 14 Jun 2006 14:09:39 -0700 [thread overview]
Message-ID: <44907B13.2030402@linux.intel.com> (raw)
In-Reply-To: <44907A8E.1080308@myri.com>
Brice Goglin wrote:er.
>
> What would you think of a patch implementing the following strategy:
> 1) if MMCONFIG works, always use it (no change)
> 2) if MMCONFIG is disabled and we are accessing the regular config
> space, use direct conf (no change, should ensure that any machine will
> still boot fine)
> 3) if MMCONFIG is disabled but we are accessing the _extended_ config
> space, try mmconfig anyway since there's no other way to do it.
an OS isn't allowed to mix old and new access methods realistically so I don't think
this is a viable good solution...
next prev parent reply other threads:[~2006-06-14 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-14 21:07 [RFC] PCI extended conf space when MMCONFIG disabled because of e820 Brice Goglin
2006-06-14 21:09 ` Arjan van de Ven [this message]
2006-06-15 1:45 ` Andi Kleen
2006-06-15 1:57 ` Brice Goglin
2006-06-15 6:47 ` Arjan van de Ven
2006-06-21 22:19 ` Rajesh Shah
2006-06-21 22:32 ` Andi Kleen
2006-06-22 0:15 ` Rajesh Shah
2006-06-22 9:27 ` Arjan van de Ven
2006-06-23 7:41 ` Rajesh Shah
-- strict thread matches above, loose matches on Subject: below --
2006-06-15 8:41 Chuck Ebbert
2006-06-15 13:18 ` Arjan van de Ven
2006-06-15 14:32 ` Barry Scott
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=44907B13.2030402@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=brice@myri.com \
--cc=linux-kernel@vger.kernel.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