From: Yinghai Lu <yinghai@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
linux-usb@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Sarah Sharp <sarah.a.sharp@linux.intel.com>,
Borislav Petkov <borislav.petkov@amd.com>,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [PATCH 2/3] x86: early_quirk check all dev/func in domain 0
Date: Mon, 10 Jan 2011 11:53:37 -0800 [thread overview]
Message-ID: <4D2B63C1.6050606@kernel.org> (raw)
In-Reply-To: <20110110160117.GD5275@kroah.com>
On 01/10/2011 08:01 AM, Greg KH wrote:
> On Sun, Jan 09, 2011 at 11:59:38AM -0800, Yinghai Lu wrote:
>>
>> go with all buses instead of bus0.
>
> Why? Why limit yourself here?
early stage pci access is via cf8, and we can not use domain there. aka domain is 0.
>
> What's to say I will not have a USB controller on the second domain? If
> you are going to change this, might as well be "correct", right?
later pci-quirks is still there. for the domain 0's will do it early. later pci-quirks will check it again.
>
> Or, if it really doesn't matter, stick with what we have today.
we can avoid to adjust apic timer delta with pm-timer.
Thanks
Yinghai
next prev parent reply other threads:[~2011-01-10 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D2A1152.1040903@kernel.org>
2011-01-09 19:59 ` [PATCH 1/3] pci, usb: Seperate usb handoff func to another file Yinghai Lu
2011-01-09 21:09 ` Benjamin Herrenschmidt
2011-01-10 7:01 ` Yinghai Lu
2011-01-10 9:38 ` Benjamin Herrenschmidt
2011-01-10 15:57 ` Greg KH
2011-01-09 19:59 ` [PATCH 2/3] x86: early_quirk check all dev/func in domain 0 Yinghai Lu
2011-01-10 16:01 ` Greg KH
2011-01-10 19:53 ` Yinghai Lu [this message]
2011-01-09 19:59 ` [PATCH 3/3] x86: usb handoff in early_quirk Yinghai Lu
2011-01-10 16:00 ` Greg KH
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=4D2B63C1.6050606@kernel.org \
--to=yinghai@kernel.org \
--cc=borislav.petkov@amd.com \
--cc=greg@kroah.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sarah.a.sharp@linux.intel.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.