xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@novell.com>, alex.williamson@hp.com
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: clear_IO_APIC() et al
Date: Tue, 16 Aug 2011 09:25:20 +0100	[thread overview]
Message-ID: <CA6FE800.1F49C%keir.xen@gmail.com> (raw)
In-Reply-To: <4E4A3C6C020000780005166E@nat28.tlf.novell.com>

On 16/08/2011 08:46, "Jan Beulich" <JBeulich@novell.com> wrote:

> In c/s 20650:b543acc1aaad you made clear_IO_APIC() call both
> clear_IO_APIC_pin() and clear_IO_APIC_raw(), and I don't really
> follow why the former would be necessary here - the only code
> paths we care about are boot and shutdown/crash, and hence
> all we want is clearing the actual IO-APIC RTEs (without regard
> to interrupt re-mapping).
> 
> Furthermore, even clear_IO_APIC_pin() is only called during early
> boot, so it would seem to me that we should only need the "raw"
> variant.
> 
> The context of the question is the need to add some extra code
> here to clear the remoteIRR bit if still set (e.g. during a crash), as
> that bit remaining set can otherwise lead to later confusion (during
> crash handling in the secondary kernel, and when booted through
> kexec in Xen itself).

I think Alex is @ Red Hat now, so unlikely to be of help here. You can feel
free to propose whatever fixups and cleanups you like on that function.

 -- Keir

> Jan
> 

      reply	other threads:[~2011-08-16  8:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16  7:46 clear_IO_APIC() et al Jan Beulich
2011-08-16  8:25 ` 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=CA6FE800.1F49C%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@novell.com \
    --cc=alex.williamson@hp.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).