qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Programmingkid <programmingkidx@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v4 00/19] Initial support for Hypervisor.framework
Date: Sat, 23 Dec 2017 11:02:46 -0500	[thread overview]
Message-ID: <D2037710-4C0C-4641-BECF-A405520843F0@gmail.com> (raw)
In-Reply-To: <mailman.14303.1514042036.27991.qemu-devel@nongnu.org>


> On Dec 23, 2017, at 10:13 AM, qemu-devel-request@nongnu.org wrote:
> 
> The following changes since commit 43ab9a5376c95c61ae898a222c4d04bdf60e239b:
> 
>  hw/i386/vmport: fix missing definitions with non-log trace backends (2017-12-21 22:52:28 +0000)
> 
> are available in the Git repository at:
> 
>  git://github.com/bonzini/qemu.git tags/for-upstream-hvf
> 
> for you to fetch changes up to 895f9fdf3ac5481ca5ad5763bf667cbf82aa52c4:
> 
>  i386: hvf: cleanup x86_gen.h (2017-12-22 15:02:07 +0100)
> 
> ----------------------------------------------------------------
> Initial support for the HVF accelerator

I was able to build and use this patch set. The one issue I noticed was the high CPU usage on the guest. Watching the same youtube video using VirtualBox sees significantly less CPU usage. This issue could probably be fixed in a future patch. Other than that I think these patches are ready.

       reply	other threads:[~2017-12-23 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.14303.1514042036.27991.qemu-devel@nongnu.org>
2017-12-23 16:02 ` Programmingkid [this message]
2017-12-24 11:18   ` [Qemu-devel] [PULL v4 00/19] Initial support for Hypervisor.framework Paolo Bonzini
2017-12-23  7:53 Paolo Bonzini
2018-01-08 13:43 ` Peter Maydell
2018-01-08 14:17   ` 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=D2037710-4C0C-4641-BECF-A405520843F0@gmail.com \
    --to=programmingkidx@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@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 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).