From: Rusty Russell <rusty@rustcorp.com.au>
To: "H. Peter Anvin" <hpa@zytor.com>,
Ramkumar Ramachandra <artagnon@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [QUERY] lguest64
Date: Tue, 23 Jul 2013 10:58:06 +0930 [thread overview]
Message-ID: <87zjte9iah.fsf@rustcorp.com.au> (raw)
In-Reply-To: <51E97779.3020103@zytor.com>
"H. Peter Anvin" <hpa@zytor.com> writes:
> On 07/19/2013 02:06 AM, Ramkumar Ramachandra wrote:
>> Hi,
>>
>> I tried building lguest to play with it, but was disappointed to find
>> this in the Kconfig:
>>
>> depends on X86_32
>>
>> Why is this [1]? What is so hard about supporting 64-bit machines? I
>> found a five-year old tree that claims to do lguest64 [2], but didn't
>> investigate further.
>>
>
> Please don't have us deal with another lguest unless there is a use case
> for it. We want to reduce pvops and pvops users, not increase them...
>
> -hpa
Yes, the subset of x86-64 machines for which there isn't hardware
virtualization support is pretty uninteresting.
Cheers,
Rusty.
next prev parent reply other threads:[~2013-07-23 4:25 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 [this message]
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
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=87zjte9iah.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=artagnon@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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 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.