From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Weidong Han <weidong.han@intel.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>,
Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: [PATCH 0/3] x2APIC improvement
Date: Wed, 7 Jul 2010 09:56:57 -0400 [thread overview]
Message-ID: <20100707135656.GD4823@phenom.dumpdata.com> (raw)
In-Reply-To: <4C340BF4.0@intel.com>
On Wed, Jul 07, 2010 at 01:09:08PM +0800, Weidong Han wrote:
> Konrad Rzeszutek Wilk wrote:
> >On Mon, Jul 05, 2010 at 03:07:58PM +0800, Han, Weidong wrote:
> >>The patchset improves Xen x2APIC support.
> >>
> >>Patch 1/3: allocate iommu when create a drhd
> >> A drhd is created when parse ACPI DMAR table, but drhd->iommu is not allocated until iommu setup. But iommu is needed by x2APIC which will enable interrupt remapping before iommu setup. This patch allocates iommu when create drhd. And then drhd->ecap can be removed because it's the same as iommu->ecap.
> >>
> >
> >Have these patches been tested on a machine where the number of DRHD !=
> >number of IOAPICs?
> >
> Why need to care about number of DRHD != number of IOAPICs? One DRHD
> may cover more than one IOAPICs. And there is already check if all
And the inverse might be true as well - in which case we should disable
x2APIC.
> IOAPICs have corresponding DRHD.
I understand. I am asking whether these patches have not changed that
behavior and whether you have tested for that.
next prev parent reply other threads:[~2010-07-07 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 7:07 [PATCH 0/3] x2APIC improvement Han, Weidong
2010-07-06 14:49 ` Konrad Rzeszutek Wilk
2010-07-07 5:09 ` Weidong Han
2010-07-07 13:56 ` Konrad Rzeszutek Wilk [this message]
2010-07-08 2:31 ` Weidong Han
2010-07-15 7:56 ` Han, Weidong
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=20100707135656.GD4823@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=weidong.han@intel.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).