mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Yinghai Lu <yhlu.kernel@gmail.com>,
	"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [patch 1/5] x2apic: fix reserved APIC register accesses in print_local_APIC()
Date: Fri, 5 Sep 2008 02:18:25 -0700	[thread overview]
Message-ID: <200809050218.25504.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080905081042.GD12409@elte.hu>

On Friday, September 05, 2008 1:10 am Ingo Molnar wrote:
> * Suresh Siddha <suresh.b.siddha@intel.com> wrote:
> > On Thu, Sep 04, 2008 at 04:06:31AM -0700, Ingo Molnar wrote:
> > > applied the following patches tip/irq/sparseirq:
> >
> > Ingo, Shouldn't this go to tip/x86/x2apic ? Thanks.
>
> normally yes - but this is a special case: there's existing overlap with
> other DMAR changes in irq/sparseirq (intr-remap and ioapic unification
> changes), so these followups have to go there too. Also, since they
> change the generic PCI code it's better they live in a generic topic to
> begin with. The full stack of pending changes is:
>
> 0f48966: dmar: fix dmar_parse_dev() devices_cnt error condition check
> 2283240: dmar: use list_for_each_entry_safe() in dmar_dev_scope_init()
> 3f1fdb3: dmar: initialize the return value in dmar_parse_dev()
> f12c73e: dmar: fix using early fixmap mapping for DMAR table parsing
> 1cb1158: x64, x2apic/intr-remap: disable DMA-remapping if
> Interrupt-remapping is detected (temporary quirk) 2ae2101: x64,
> x2apic/intr-remap: Interrupt remapping infrastructure fe962e9: x64,
> x2apic/intr-remap: Queued invalidation infrastructure (part of VT-d)
> ad3ad3f: x64, x2apic/intr-remap: parse ioapic scope under vt-d structures
> 2d6b5f8: x64, x2apic/intr-remap: Fix the need for RMRR in the DMA-remapping
> detection aaa9d1d: x64, x2apic/intr-remap: use CONFIG_DMAR for
> DMA-remapping specific code 1886e8a: x64, x2apic/intr-remap: code
> re-structuring, to be used by both DMA and Interrupt remapping c42d9f3:
> x64, x2apic/intr-remap: fix the need for sequential array allocation of
> iommus e61d98d: x64, x2apic/intr-remap: Intel vt-d, IOMMU code
> reorganization
>
> Jesse, do you have any objections to this approach?

Nope, no problems.  I think I have some pending patches that may have 
conflicts with the above, but I'll take care of that when I get back to the 
US (I think Sunday or Monday will be a massive patch review/merge/comment 
day).

Thanks,
Jesse

      reply	other threads:[~2008-09-05  9:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03 23:58 Suresh Siddha
2008-09-03 23:58 ` [patch 2/5] dmar: fix using early fixmap mapping for DMAR table parsing Suresh Siddha
2008-09-03 23:58 ` [patch 3/5] dmar: initialize the return value in dmar_parse_dev() Suresh Siddha
2008-09-03 23:58 ` [patch 4/5] dmar: use list_for_each_entry_safe() in dmar_dev_scope_init() Suresh Siddha
2008-09-03 23:58 ` [patch 5/5] dmar: fix dmar_parse_dev() devices_cnt error condition check Suresh Siddha
2008-09-04 11:06 ` [patch 1/5] x2apic: fix reserved APIC register accesses in print_local_APIC() Ingo Molnar
2008-09-04 17:51   ` Suresh Siddha
2008-09-05  8:10     ` Ingo Molnar
2008-09-05  9:18       ` Jesse Barnes [this message]

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=200809050218.25504.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@gmail.com \
    /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

Powered by JetHome