From: "Jan Beulich" <JBeulich@suse.com>
To: "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>
Cc: <david.vrabel@Citrix.com>, <konrad@kernel.org>,
<xen-devel@lists.xenproject.org>, <boris.ostrovsky@oracle.com>,
<linux-kernel@vger.kernel.org>, <keir@xen.org>
Subject: Re: [LINUX PATCH 2/2] xen/pvhvm: Support more than 32 VCPUs when migrating.
Date: Wed, 09 Apr 2014 11:21:03 +0100 [thread overview]
Message-ID: <53453B2F0200007800007119@nat28.tlf.novell.com> (raw)
In-Reply-To: <201404091015.s39AFQAu022348@aserz7021.oracle.com>
>>> On 09.04.14 at 12:15, <konrad.wilk@oracle.com> wrote:
> On Apr 9, 2014 4:03 AM, Jan Beulich <JBeulich@suse.com> wrote:
>>
>> >>> On 08.04.14 at 19:25, <konrad@kernel.org> wrote:
>> > + /* Only Xen 4.5 and higher supports this. */
>> > + if (HYPERVISOR_vcpu_op(VCPUOP_is_up, smp_processor_id(), NULL) ==
> -ENOSYS)
>> > + vcpuops = false;
>>
>> Did you mean to say "for HVM guests" in the comment? And of
>> course the comment could quickly become stale if we backported
>> the Xen side change to e.g. 4.4.1.
>>
>
> Right. But I thought that features like that (new hypercalls) wasn't
> applicable for backporting?
It's not really a new hypercall, and fixing a problem, so I'd consider
it a candidate at least for 4.4.1.
Jan
next prev parent reply other threads:[~2014-04-09 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 10:15 Konrad Rzeszutek Wilk
2014-04-09 10:21 ` Jan Beulich [this message]
[not found] <1396859560.22845.4.camel@kazak.uk.xensource.com>
2014-04-08 17:25 ` [PATCH] Fixes for more than 32 VCPUs migration for HVM guests (v1) konrad
2014-04-08 17:25 ` [LINUX PATCH 2/2] xen/pvhvm: Support more than 32 VCPUs when migrating konrad
2014-04-09 8:03 ` Jan Beulich
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=53453B2F0200007800007119@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@Citrix.com \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=konrad@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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®