From: Yinghai Lu <yinghai@kernel.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>,
Tvrtko Ursulin <tvrtko@ursulin.net>,
Tvrtko Ursulin <tvrtko.ursulin@sophos.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: Are these MTRR settings correct?
Date: Tue, 15 Dec 2009 22:26:32 -0800 [thread overview]
Message-ID: <86802c440912152226n26cde7f1mfa42273e9592dcbf@mail.gmail.com> (raw)
In-Reply-To: <51f3faa70912151250y709a42c8l91012a64ef21a476@mail.gmail.com>
On Tue, Dec 15, 2009 at 12:50 PM, Robert Hancock <hancockrwd@gmail.com> wrote:
This was solved by using MMCONFIG
> for extended config space access only, so that when we move the BAR
> temporarily during sizing, we're not trying to access the MMCONFIG
> region it overlaps (since BAR sizing requires only base access).
how about IOV bar 0x184 and 190 ?
YH
next prev parent reply other threads:[~2009-12-16 6:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-13 8:07 Are there " Tvrtko Ursulin
2009-12-13 8:26 ` Are these " Tvrtko Ursulin
2009-12-13 9:25 ` Yinghai Lu
2009-12-13 17:19 ` Tvrtko Ursulin
2009-12-13 22:56 ` Yinghai Lu
2009-12-14 11:19 ` Tvrtko Ursulin
2009-12-14 11:25 ` Yinghai Lu
2009-12-14 19:34 ` Tvrtko Ursulin
2009-12-14 19:47 ` Yinghai Lu
2009-12-14 20:16 ` Tvrtko Ursulin
2009-12-14 20:26 ` Yinghai Lu
2009-12-15 1:22 ` Robert Hancock
2009-12-15 1:42 ` Yinghai Lu
2009-12-15 16:55 ` Bjorn Helgaas
2009-12-15 18:01 ` Yinghai Lu
2009-12-15 20:50 ` Robert Hancock
2009-12-15 21:09 ` Jesse Barnes
2009-12-16 0:14 ` Robert Hancock
2009-12-16 6:26 ` Yinghai Lu [this message]
2009-12-15 2:47 ` [PATCH] x86/pci: don't check mmconf again if it is from MSR with amd faml0h Yinghai Lu
2009-12-16 20:06 ` Jesse Barnes
2009-12-16 22:18 ` Yinghai Lu
2009-12-13 20:26 ` Are these MTRR settings correct? Robert Hancock
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=86802c440912152226n26cde7f1mfa42273e9592dcbf@mail.gmail.com \
--to=yinghai@kernel.org \
--cc=bjorn.helgaas@hp.com \
--cc=hancockrwd@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko.ursulin@sophos.com \
--cc=tvrtko@ursulin.net \
/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
all inboxes | Powered by JetHome®