From: Konrad Rzeszutek Wilk <konrad@darnok.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH] xen pvhvm: do not remap pirqs onto evtchns if !xen_have_vector_callback
Date: Tue, 31 Jan 2012 21:08:03 -0400 [thread overview]
Message-ID: <20120201010803.GD32295@andromeda.dapyr.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1201311636380.3196@kaball-desktop>
On Tue, Jan 31, 2012 at 04:40:26PM +0000, Stefano Stabellini wrote:
> On Tue, 31 Jan 2012, Konrad Rzeszutek Wilk wrote:
> > On Mon, Jan 30, 2012 at 02:31:46PM +0000, Stefano Stabellini wrote:
> > >
> > > Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> >
> > So the xen_have_vector_callback looks to be only set by
> >
> > 1398 if (xen_feature(XENFEAT_hvm_callback_vector))
> > 1399 xen_have_vector_callback = 1;
> >
> > So could this be just done via a check for that instead?
> >
>
> Sure, but I don't think it would be better: using
> xen_have_vector_callback is more consistent and give us the flexibility
> of allowing users to manually override it in the future.
ok. applied. Hm, I was thinking to put on stable@kernel.org - but how
far back should it go? 2.6.37?
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2012-02-01 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 14:31 Stefano Stabellini
2012-01-31 16:27 ` Konrad Rzeszutek Wilk
2012-01-31 16:40 ` Stefano Stabellini
2012-02-01 1:08 ` Konrad Rzeszutek Wilk [this message]
2012-02-01 11:09 ` [Xen-devel] " Stefano Stabellini
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=20120201010803.GD32295@andromeda.dapyr.net \
--to=konrad@darnok.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®