From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Kamil Rytarowski <n54@gmx.com>,
Alexandro Sanchez Bach <asanchez@kryptoslogic.com>,
qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
yu.ning@intel.com, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] hax: Support for Linux hosts
Date: Wed, 9 Jan 2019 12:00:03 +0100 [thread overview]
Message-ID: <af8e1f23-27e2-3a7e-b911-0abda449dbf2@redhat.com> (raw)
In-Reply-To: <075402ba-b1f1-b7d1-3a6a-47b6dd959133@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1690 bytes --]
On 1/8/19 7:27 PM, Paolo Bonzini wrote:
> On 08/01/19 18:12, Kamil Rytarowski wrote:
>> On 25.11.2018 18:14, Paolo Bonzini wrote:
>>> On 25/11/18 00:50, Kamil Rytarowski wrote:
>>>> On 22.11.2018 08:24, Kamil Rytarowski wrote:
>>>>> On 16.11.2018 13:52, Paolo Bonzini wrote:
>>>>>> 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
>>>>>>
>>>>>
>>>>> This patch is also useful for NetBSD, even if it's not a Linux host.
>>>>> There is a driver in progress again (thanks to the newly added Linux
>>>>> port, it's now much easier to get done).
>>>>>
>>>>> I recommend to merge this patch.
>>>>>
>>>>
>>>> For the record, I've a functional version of HAXM for NetBSD as host.
>>>> Once you will merge this patch, I will submit another one to configure
>>>> to enable haxm for NetBSD.
>>>>
>>>> I need to keep the patch by Alexandro in a local copy of qemu.
>>>
>>> Sure, it will be accepted for the release after 3.1.
>>>
>>> Paolo
>>>
>>>
>>
>> Ping.
>
> It's already queued, but the pull request was pretty big and it had some
> issues (quite an understatement).
Hopefully you queued Alexandro's v2 (which isn't named v2) with Alex
comments fixed, thanks!
Phil.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-09 11:00 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
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é [this message]
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=af8e1f23-27e2-3a7e-b911-0abda449dbf2@redhat.com \
--to=philmd@redhat.com \
--cc=asanchez@kryptoslogic.com \
--cc=ehabkost@redhat.com \
--cc=n54@gmx.com \
--cc=pbonzini@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).