public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Mike Rapoport <mike.rapoport@gmail.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [QUERY] lguest64
Date: Thu, 01 Aug 2013 11:42:29 +0930	[thread overview]
Message-ID: <8761vq40s2.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CABpLfoiKnbkHq9oT3yk72583yYKz_AMotLVV-Cu1sw1B1GH0xw@mail.gmail.com>

Mike Rapoport <mike.rapoport@gmail.com> writes:
> On Wed, Jul 31, 2013 at 3:17 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> On 07/31/2013 02:39 AM, Mike Rapoport wrote:
>>>
>>> The use case I had in mind is to use lguest as a nested hypervisor in
>>> public clouds. As of today, major public clouds do not support nested
>>> virtualization and it's not clear at all if they will expose this
>>> ability in their deployments. Addition of 64-bit support for lguest
>>> won't require changes to pvops and, as far as I can tell, won't change
>>> the number of pvops users...
>>>
>>
>> "We can add a pvops user and that won't change the number of pvops
>> users" What?!
>
> We modify existing pvops user, IMHO. lguest is existing pvops user and
> my idea was to extend it, rather than add lguest64 alongside lguest32.

Well, lguest is particularly expendable.  It's the red shirt of the
virtualization away team.

Unlike HPA, I would advocate for applying the patches if you produced
them.  But I'd be aware that they're likely to be ripped out as soon as
pvops has no other users.

Cheers,
Rusty.

  parent reply	other threads:[~2013-08-02  2:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19  9:06 [QUERY] lguest64 Ramkumar Ramachandra
2013-07-19 17:29 ` H. Peter Anvin
2013-07-19 17:42   ` Ramkumar Ramachandra
2013-07-19 18:46     ` H. Peter Anvin
2013-07-19 20:36       ` richard -rw- weinberger
2013-08-01 17:22       ` Ramkumar Ramachandra
2013-08-01 13:04         ` Alex Elsayed
2013-07-23  1:28   ` Rusty Russell
2013-07-31  9:39     ` Mike Rapoport
2013-07-31 12:17       ` H. Peter Anvin
2013-07-31 13:07         ` Mike Rapoport
2013-07-31 13:19           ` H. Peter Anvin
2013-07-31 14:32             ` Mike Rapoport
2013-08-01  2:12           ` Rusty Russell [this message]
2013-08-02 14:27             ` H. Peter Anvin
2013-07-31 13:17         ` Konrad Rzeszutek Wilk
2013-07-31 13:25           ` H. Peter Anvin
2013-08-02 19:09             ` Konrad Rzeszutek Wilk
2013-08-04 12:37               ` Gleb Natapov
2013-08-05 16:50                 ` Konrad Rzeszutek Wilk
2013-08-05 16:59                   ` H. Peter Anvin
2013-08-05 17:16                     ` Konrad Rzeszutek Wilk
2013-07-31 15:31       ` Borislav Petkov
2013-08-01  7:18         ` Mike Rapoport
2013-08-08 19:15       ` Richard W.M. Jones

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=8761vq40s2.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=artagnon@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.rapoport@gmail.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