[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8761vq40s2.fsf@rustcorp.com.au>
Date: Thu, 01 Aug 2013 11:42:29 +0930
From: Rusty Russell <rusty@...tcorp.com.au>
To: Mike Rapoport <mike.rapoport@...il.com>,
"H. Peter Anvin" <hpa@...or.com>
Cc: Ramkumar Ramachandra <artagnon@...il.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [QUERY] lguest64
Mike Rapoport <mike.rapoport@...il.com> writes:
> On Wed, Jul 31, 2013 at 3:17 PM, H. Peter Anvin <hpa@...or.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists