From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH, resend] replacement for noirqdebug hack
Date: Thu, 08 Jun 2006 09:00:40 +0200 [thread overview]
Message-ID: <4487E738.76E4.0078.0@novell.com> (raw)
In-Reply-To: <2d952ccdfba10b96dadf09495853dcdf@cl.cam.ac.uk>
>>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 07.06.06 17:57 >>>
>
>How about the following patch, which is a cleaner modification to Linux
>and does not affect shared_info layout? Note that it depends on a Xen
>patch that is currently in the staging tree (extends the irq info
>hypercall to inform about sharing status), and that the patch is
>against xen-unstable. The status check is much slower than reading from
>shared memory, but ought to be on a rare path (unless you have a
>high-rate interrupt line shared across guests, which is going to be
>rather suckful anyway).
Yes, that looks fine to me (assuming that the other patch you mention is the one introducing
PHYSDEVOP_irq_status_query, and that this is a non-intrusive addition).
Jan
prev parent reply other threads:[~2006-06-08 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 10:02 [PATCH, resend] replacement for noirqdebug hack Jan Beulich
2006-06-02 10:32 ` Keir Fraser
2006-06-02 11:01 ` Jan Beulich
2006-06-02 11:09 ` Keir Fraser
2006-06-07 15:57 ` Keir Fraser
2006-06-08 7:00 ` Jan Beulich [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=4487E738.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--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.