All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: ACPI-Tables corrupted?
Date: Wed, 28 Jul 2010 15:27:54 +0200	[thread overview]
Message-ID: <4C50305A.8070209@ts.fujitsu.com> (raw)
In-Reply-To: <C875E4E8.1BE14%keir.fraser@eu.citrix.com>

On 07/28/2010 02:45 PM, Keir Fraser wrote:
> On 28/07/2010 13:13, "Juergen Gross"<juergen.gross@ts.fujitsu.com>  wrote:
>
>>>> As Dom0 is a pv-kernel, it should be able to ignore this entry.
>>>> The crash kernel OTOH should not panic due to the trashed entry!
>>>> What is the correct solution here?
>>>
>>> Could provide a cmdline option to not nobble the DMAR?
>>
>> That's a possibility.
>> I wonder whether it wouldn't be better to let dom0 decide not to use it if
>> running under xen. This would remove the requirement for zapping the ACPI
>> table. IMO it's always a bad idea to change data of a deeper layer...
>
> If we don't zap the DMAR then every existing dom0 kernel will fail with new
> hypervisor. We could gate it on a new elfnote, or rename to XMAR and have
> dom0 rename it back, or just have a flag day.

The really clean solution would be to virtualize the ACPI table for dom0 and
remove the DMAR entry in this version. This would require some major work, I
guess (clone at least the BIOS page containing the ACPI anchor and present
a modified version to dom0).

>
>>>> The crash kernel expects a valid DMAR entry, as following code in
>>>> enable_IR_x2apic() suggests:
>>>
>>> I don't know what that function does, nor how the error path below depends
>>> on DMAR. DMAR isn't mentioned in the below code.
>>
>> Sorry, here a larger fragment (source arch/x86/kernel/apic/apic.c):
>>                   /* IR is required if there is APIC ID>  255 even when running
>>                    * under KVM
>>                    */
>>                   if (max_physical_apicid>  255 || !kvm_para_available())
>>                           goto nox2apic;
>
> The if stmt is confusing. Also, what would happen if this kernel was booted
> on a system without VT-d (and hence no DMAR)? Presumably it *can* boot in a
> DMAR-less environment -- there must be something odd going on for it to end
> on this path for us.

Yeah, that puzzled me, too.


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

  reply	other threads:[~2010-07-28 13:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28  9:38 ACPI-Tables corrupted? Juergen Gross
2010-07-28 10:03 ` Keir Fraser
2010-07-28 11:26   ` Juergen Gross
2010-07-28 11:39     ` Keir Fraser
2010-07-28 12:13       ` Juergen Gross
2010-07-28 12:45         ` Keir Fraser
2010-07-28 13:27           ` Juergen Gross [this message]
2010-07-28 13:36             ` Konrad Rzeszutek Wilk
2010-07-29  6:19               ` Juergen Gross
2010-07-29  6:39                 ` Keir Fraser
2010-07-29  6:48                   ` Juergen Gross
2010-07-29  6:48                     ` Keir Fraser
2010-07-29  6:53                       ` Juergen Gross
2010-08-06 13:39           ` Jan Beulich
2010-08-06 14:04             ` Keir Fraser
2010-07-29  6:31         ` Jiang, Yunhong
2010-07-29  6:40           ` Keir Fraser
2010-07-29  6:48             ` Keir Fraser
2010-07-29  7:37               ` Jiang, Yunhong
2010-07-29  9:04                 ` Juergen Gross
2010-07-29  9:33                 ` Keir Fraser
2010-07-29 10:24             ` Keir Fraser
2010-07-30  4:47               ` Juergen Gross

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=4C50305A.8070209@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=keir.fraser@eu.citrix.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 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.