All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
	778737@bugs.debian.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-trivial] configure: enable kvm on x32
Date: Thu, 12 Mar 2015 15:18:38 +0100	[thread overview]
Message-ID: <5501A03E.7080301@redhat.com> (raw)
In-Reply-To: <550148F0.4030108@msgid.tls.msk.ru>



On 12/03/2015 09:06, Michael Tokarev wrote:
> 12.03.2015 10:16, Peter Maydell wrote:
>> On 12 March 2015 at 06:13, Michael Tokarev <mjt@tls.msk.ru> wrote:
>>> Here's a trivial change to enable kvm on x32 architecture.
>>> I'm not 100% sure the result works correctly in all cases,
>>> but this is a good start and in theory everything should
>>> work.
>>
>> Given the pessimism expressed in this comment, perhaps
>> we should delay this to 2.4 and when it's had more
>> testing?
> 
> There's no pessimism really.  It is a new arch for kvm, so
> _something_ might not work.  In practice it works fairy well,
> see https://bugs.debian.org/778737 -- at least debian can
> be installed in x32 kvm.
> 
> And we don't lose anything really because it is a new arch.
> 
> That's why it was Cc'd -trivial.

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

... but I'm not going to test it.

Paolo


WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
	Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
	778737@bugs.debian.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] configure: enable kvm on x32
Date: Thu, 12 Mar 2015 15:18:38 +0100	[thread overview]
Message-ID: <5501A03E.7080301@redhat.com> (raw)
In-Reply-To: <550148F0.4030108@msgid.tls.msk.ru>



On 12/03/2015 09:06, Michael Tokarev wrote:
> 12.03.2015 10:16, Peter Maydell wrote:
>> On 12 March 2015 at 06:13, Michael Tokarev <mjt@tls.msk.ru> wrote:
>>> Here's a trivial change to enable kvm on x32 architecture.
>>> I'm not 100% sure the result works correctly in all cases,
>>> but this is a good start and in theory everything should
>>> work.
>>
>> Given the pessimism expressed in this comment, perhaps
>> we should delay this to 2.4 and when it's had more
>> testing?
> 
> There's no pessimism really.  It is a new arch for kvm, so
> _something_ might not work.  In practice it works fairy well,
> see https://bugs.debian.org/778737 -- at least debian can
> be installed in x32 kvm.
> 
> And we don't lose anything really because it is a new arch.
> 
> That's why it was Cc'd -trivial.

Acked-by: Paolo Bonzini <pbonzini@redhat.com>

... but I'm not going to test it.

Paolo

  reply	other threads:[~2015-03-12 14:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12  6:13 [Qemu-trivial] configure: enable kvm on x32 Michael Tokarev
2015-03-12  6:13 ` [Qemu-devel] " Michael Tokarev
2015-03-12  7:16 ` [Qemu-trivial] " Peter Maydell
2015-03-12  7:16   ` Peter Maydell
2015-03-12  8:06   ` [Qemu-trivial] " Michael Tokarev
2015-03-12  8:06     ` [Qemu-devel] " Michael Tokarev
2015-03-12 14:18     ` Paolo Bonzini [this message]
2015-03-12 14:18       ` Paolo Bonzini

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=5501A03E.7080301@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=778737@bugs.debian.org \
    --cc=mjt@tls.msk.ru \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.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.