As a HAXM developer at Intel, I just want to come out and show our
support for Vincent's upstreaming effort. We'd love to see HAXM support
code land in upstream QEMU, and will do what is necessary to make that
happen.
We've been working on the issues that Vincent raised and have made some
h just a FIXME comment, but... Yu
Ning, can you tell us what user_event_pending is for? :) My hunch is
that we should call hax_raise_event after setting cpu->exit_request, like
hax_raise_event();
/* write user_event_pending before exit_request */
smp_wmb();
h is
not supported by HAXM kernel module at this time.
Signed-off-by: Yu Ning <yu.n...@linux.intel.com>
---
target/i386/hax-mem.c | 19 +--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/target/i386/hax-mem.c b/target/i386/hax-mem.c
index 2884040..af09034 100644
On 11/15/2017 3:13, John Snow wrote:
On 11/14/2017 06:09 AM, Thomas Huth wrote:
That's great news! I hope this all will help to promote QEMU on Windows
and macOS quite a bit!
However, during the past months, I noticed a couple of times that users
ask on IRC or the qemu-discuss mailing list
On 11/23/2017 1:03, Thomas Huth wrote:
On 22.11.2017 15:52, Yu Ning wrote:
On 11/22/2017 20:25, Thomas Huth wrote:
[...]
Would it be OK to remove the qemu-debian-wheezy-gui-with-haxm.png from
the blog post?
Yes, I'm fine with removing it. Sorry I haven't installed Jekyll and
didn't test
On 11/22/2017 20:25, Thomas Huth wrote:
On 22.11.2017 09:10, Yu Ning wrote:
From: Yu Ning <yu.n...@intel.com>
Following my announcement of the open source release of HAXM,
I was asked to write a blog post for normal Windows users to
advertise the use of "-accel hax":
https
On 11/29/2017 9:25, Fam Zheng wrote:
On Tue, 11/28 13:57, Eric Blake wrote:
On 11/22/2017 04:43 AM, no-re...@patchew.org wrote:
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
On 11/15/2017 22:18, Paolo Bonzini wrote:
On 15/11/2017 09:25, Yu Ning wrote:
On 11/15/2017 3:13, John Snow wrote:
On 11/14/2017 06:09 AM, Thomas Huth wrote:
That's great news! I hope this all will help to promote QEMU on Windows
and macOS quite a bit!
However, during the past months, I
On 11/17/2017 16:30, Thomas Huth wrote:
On 17.11.2017 09:17, Yu Ning wrote:
[...]
Is there a preferred document format for the QEMU blog, e.g. Markdown?
Yes, we're using markdown of Jekyll (https://jekyllrb.com/docs/posts/).
Please clone the qemu-web repository (see
https://git.qemu.org/?p
On 11/17/2017 2:00, Eduardo Habkost wrote:
On Thu, Nov 16, 2017 at 07:47:44AM +0100, Stefan Weil wrote:
Am 16.11.2017 um 07:50 schrieb yu.n...@linux.intel.com:
From: Yu Ning <yu.n...@intel.com>
hax-interface.h defines the interface between the HAXM kernel
module and the HAX
On 11/17/2017 16:53, Kamil Rytarowski wrote:
On 14.11.2017 09:54, Yu Ning wrote:
Hello,
As some of you may have noticed, since QEMU 2.9.0, an accelerator known
as “hax” has been available for Windows and macOS builds of QEMU, thanks
to the hard work of Vincent Palatin and help from
Hello,
As some of you may have noticed, since QEMU 2.9.0, an accelerator known
as “hax” has been available for Windows and macOS builds of QEMU, thanks
to the hard work of Vincent Palatin and help from this community (Paolo
Bonzini, Stefan Weil, et al.).
The accelerator requires a host
On 11/20/2017 5:31, Eduardo Habkost wrote:
On Fri, Nov 17, 2017 at 05:03:27PM +0800, Yu Ning wrote:
On 11/17/2017 2:00, Eduardo Habkost wrote:
On Thu, Nov 16, 2017 at 07:47:44AM +0100, Stefan Weil wrote:
Am 16.11.2017 um 07:50 schrieb yu.n...@linux.intel.com:
From: Yu Ning <y
From: Yu Ning <yu.n...@intel.com>
hax-interface.h defines the interface between the HAXM kernel
module and the HAXM QEMU accelerator. The same code can be found in
the following files of the HAXM kernel module:
include/hax_interface.h
include/vcpu_state.h
core/include/vm.h
These
A gentle ping. Patchwork link: http://patchwork.ozlabs.org/patch/859715/
On 1/12/2018 18:22, Yu Ning wrote:
From: Yu Ning <yu.n...@intel.com>
Since HAX_VM_IOCTL_ALLOC_RAM takes a 32-bit size, it cannot handle
RAM blocks of 4GB or larger, which is why HAXM can only run guests
with les
From: Yu Ning <yu.n...@intel.com>
Since HAX_VM_IOCTL_ALLOC_RAM takes a 32-bit size, it cannot handle
RAM blocks of 4GB or larger, which is why HAXM can only run guests
with less than 4GB of RAM. Solve this problem by utilizing the new
HAXM API, HAX_VM_IOCTL_ADD_RAMBLOCK, which takes a 64-bi
On 2/7/2018 7:36, Paolo Bonzini wrote:
Queued, thanks. Sorry for the delay!
That's okay, thanks!
Yu
Paolo
)?
The main person working on HAXM is Yu Ning. Anthony and Glauber are
only listed because they are the authors of the KVM support (and HAXM
support in turn is based on KVM).
That is correct, and thanks Paolo for the introduction. In fact I just
reviewed a HAXM pull request from Alexandro on GitHub, so
Hello,
I am leaving Intel, and will soon lose access to my Intel email
accounts. Effective today, I am no longer maintainer of the HAXM open
source project (https://github.com/intel/haxm). Colin Xu (colin DOT xu
AT intel DOT com) will take my place, and he will be helped by Henry
Yuan (hang
19 matches
Mail list logo
