qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexandro Sanchez Bach <asanchez@kryptoslogic.com>,
	qemu-devel@nongnu.org
Cc: yu.ning@intel.com, Richard Henderson <rth@twiddle.net>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] hax: Support for Linux hosts
Date: Fri, 16 Nov 2018 13:52:45 +0100	[thread overview]
Message-ID: <1782562d-41c7-0cc7-94f3-fb7ff4b7bd40@redhat.com> (raw)
In-Reply-To: <20181114130428.32326-1-asanchez@kryptoslogic.com>

On 14/11/18 14:04, Alexandro Sanchez Bach wrote:
> Intel HAXM supports now 32-bit and 64-bit Linux hosts. This patch includes
> the corresponding userland changes.
> 
> Since the Darwin userland backend is POSIX-compliant, the hax-darwin.{c,h}
> files have been renamed to hax-posix.{c,h}. This prefix is consistent with
> the naming used in the rest of QEMU.

What's the advantage of HAXM when Linux hosts can just run KVM?  I guess
avoiding bitrot?

Paolo

  parent reply	other threads:[~2018-11-16 12:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14 13:04 [Qemu-devel] [PATCH] hax: Support for Linux hosts Alexandro Sanchez Bach
2018-11-14 15:04 ` Alex Bennée
2018-11-15  1:33   ` Alexandro Sanchez Bach
2018-11-16 12:52 ` Paolo Bonzini [this message]
2018-11-16 15:00   ` Alexandro Sanchez
2018-11-22  7:24   ` Kamil Rytarowski
2018-11-24 23:50     ` Kamil Rytarowski
2018-11-25 17:14       ` Paolo Bonzini
2019-01-08 17:12         ` Kamil Rytarowski
2019-01-08 18:27           ` Paolo Bonzini
2019-01-09 11:00             ` Philippe Mathieu-Daudé
2019-02-02 15:03         ` Kamil Rytarowski
  -- strict thread matches above, loose matches on Subject: below --
2018-11-08 11:11 Alexandro Sanchez Bach

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=1782562d-41c7-0cc7-94f3-fb7ff4b7bd40@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=asanchez@kryptoslogic.com \
    --cc=ehabkost@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=yu.ning@intel.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;
as well as URLs for NNTP newsgroup(s).