xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 0 of 6] Fix kexec in Xen (take 3)
Date: Thu, 26 May 2011 10:19:59 +0100	[thread overview]
Message-ID: <CA03D9CF.2DABE%keir@xen.org> (raw)
In-Reply-To: <4DDE1961.80303@citrix.com>

On 26/05/2011 10:12, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:

>> A better reference for APIC behaviour is Chapter 10 of Volume 3A of the
>> Intel Software Developer Manual. See 10.4.7.1 particularly. The APIC is
>> software disabled on startup -- meaning that the enable bit in the SPIV
>> register is clear. That is quite different from *hardware* disable (via the
>> APICBASE MSR) which your patch attempts to deal with. In this latter case
>> the APIC would be totally shut down and it would not be possible to
>> INIT-SIPI the secondary processor. The software disable (via SPIV) is very
>> much a semi-disabled state (and disable_local_APIC() already returns an APIC
>> to that state).
>> 
>>   -- Keir
>> 
> Ok - I will read up on this more, and then I guess I have some code to
> change.

Yes, please do.

Also if you can please try to avoid making crash-specific versions of
cleanup/shutdown functions. I would actually rather have a global variable
indicating I-am-crashing-on-cpu-x, and have at that from the existing
shutdown functions to modify their behaviour.

If you can fix that plus curb your impulse to do more to the APIC code than
necessary then we have a starting point for further review.

 -- Keir

      reply	other threads:[~2011-05-26  9:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 14:32 [PATCH 0 of 6] Fix kexec in Xen (take 3) Andrew Cooper
2011-05-25 14:32 ` [PATCH 1 of 6] APIC: record local APIC state on boot Andrew Cooper
2011-05-25 14:32 ` [PATCH 2 of 6] APIC: remove 'enabled_via_apicbase' variable Andrew Cooper
2011-05-25 14:32 ` [PATCH 3 of 6] APIC: add crash_disable_local_APIC Andrew Cooper
2011-05-25 14:32 ` [PATCH 4 of 6] IOMMU: Sanitise some of our pointer work Andrew Cooper
2011-05-25 17:28   ` Konrad Rzeszutek Wilk
2011-05-25 14:32 ` [PATCH 5 of 6] IOMMU: add crash_shutdown iommu_op Andrew Cooper
2011-05-25 14:32 ` [PATCH 6 of 6] KEXEC: disable iommu jumping into the kdump kernel Andrew Cooper
2011-05-25 15:01 ` [PATCH 0 of 6] Fix kexec in Xen (take 3) Wei Wang2
2011-05-25 16:14 ` Jan Beulich
2011-05-25 16:30   ` Andrew Cooper
2011-05-25 21:35     ` Keir Fraser
2011-05-26  9:12       ` Andrew Cooper
2011-05-26  9:19         ` Keir Fraser [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=CA03D9CF.2DABE%keir@xen.org \
    --to=keir@xen.org \
    --cc=andrew.cooper3@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 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).