From: "Jan Beulich" <JBeulich@novell.com>
To: Allen M Kay <allen.m.kay@intel.com>
Cc: Joseph Cihula <joseph.cihula@intel.com>,
Keir Fraser <keir@xen.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH][VTD] check BIOS settings before enabling interrupt remapping or x2apic
Date: Tue, 05 Apr 2011 11:41:58 +0100 [thread overview]
Message-ID: <4D9B0E160200007800039FA5@vpn.id2.novell.com> (raw)
In-Reply-To: <987664A83D2D224EAE907B061CE93D5301A79A3BDF@orsmsx505.amr.corp.intel.com>
>>> On 29.03.11 at 19:58, "Kay, Allen M" <allen.m.kay@intel.com> wrote:
> Check flags field in ACPI DMAR structure before enabling interrupt remapping
> or x2apic. This allows platform vendors to disable interrupt remapping or
> x2apic features if on board BIOS does not support them.
>
> Signed-off-by: Allen Kay <allen.m.kay@intel.com>
Taking a second look (while trying to merge this into our SLE11
code base), I think this
>@@ -761,7 +762,11 @@ out:
>
> int __init acpi_dmar_init(void)
> {
>+ struct acpi_table_dmar *dmar;
>+
> acpi_get_table(ACPI_SIG_DMAR, 0, &dmar_table);
>+ dmar = (struct acpi_table_dmar *) dmar_table;
>+ dmar_flags = dmar->flags;
>
> return parse_dmar_table(acpi_parse_dmar);
> }
is wrong from a TXT perspective - the table obtained here must
only be used for the signature zapping activity, nothing else. All
decisions must be based upon what gets passed to
acpi_parse_dmar(). (This would at once reduce the size of
the change, since a cast struct acpi_table_dmar * is already
available there.)
Jan
next prev parent reply other threads:[~2011-04-05 10:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 17:58 [PATCH][VTD] check BIOS settings before enabling interrupt remapping or x2apic Kay, Allen M
2011-04-05 10:41 ` Jan Beulich [this message]
2011-04-05 18:13 ` Kay, Allen M
2011-04-06 6:40 ` Jan Beulich
2011-04-06 5:38 ` Wei, Gang
2011-04-05 10:53 ` Jan Beulich
2011-04-05 18:10 ` Kay, Allen M
2011-04-06 6:39 ` Jan Beulich
2011-04-06 7:40 ` Keir Fraser
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=4D9B0E160200007800039FA5@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=allen.m.kay@intel.com \
--cc=joseph.cihula@intel.com \
--cc=keir@xen.org \
--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).