From: Lukas Straub <lukasstraub2@web.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: pbonzini@redhat.com, Cameron Esfahani <dirty@apple.com>
Subject: Re: [PATCH 0/5] hvf: stability fixes for HVF
Date: Sun, 24 Nov 2019 13:17:30 +0100 [thread overview]
Message-ID: <20191124131730.19ad6bf1@luklap> (raw)
In-Reply-To: <cover.1574375668.git.dirty@apple.com>
On Thu, 21 Nov 2019 14:54:49 -0800
Cameron Esfahani via <qemu-devel@nongnu.org> wrote:
> The following patches fix stability issues with running QEMU on Apple
> Hypervisor Framework (HVF):
> - non-RAM, non-ROMD areas need to trap so accesses can be correctly
> emulated.
> - Current TSC synchronization implementation is insufficient: when
> running with more than 1 core, TSC values can go backwards. Until
> a correct implementation can be written, remove calls to
> hv_vm_sync_tsc(). Pass through TSC to guest OS.
> - Fix REX emulation in relation to legacy prefixes.
> - More correctly match SDM when setting CR0 and PDPTE registers.
> - Save away exception type as well as vector in hvf_store_events() so
> they can be correctly reinjected in hvf_inject_interrupts(). Under
> heavy loads, exceptions got misrouted.
>
> Cameron Esfahani (5):
> hvf: non-RAM, non-ROMD memory ranges are now correctly mapped in
> hvf: remove TSC synchronization code because it isn't fully complete
> hvf: correctly handle REX prefix in relation to legacy prefixes
> hvf: more accurately match SDM when setting CR0 and PDPTE registers
> hvf: save away type as well as vector so we can reinject them
>
> target/i386/hvf/hvf.c | 74 +++++++++++++++++++++++++-----------
> target/i386/hvf/vmx.h | 18 +++++----
> target/i386/hvf/x86_decode.c | 55 ++++++++++++++-------------
> target/i386/hvf/x86_decode.h | 16 ++++----
> target/i386/hvf/x86_emu.c | 3 --
> target/i386/hvf/x86hvf.c | 26 +++++--------
> 6 files changed, 108 insertions(+), 84 deletions(-)
>
Hi,
I can't comment on your code, but simply resend this as v2 with the
checkpatch.pl errors fixed. You can run checkpatch.pl locally before
posting (scripts/checkpatch.pl).
Regards,
Lukas Straub
prev parent reply other threads:[~2019-11-24 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 22:54 [PATCH 0/5] hvf: stability fixes for HVF Cameron Esfahani via
2019-11-21 22:54 ` [PATCH 1/5] hvf: non-RAM, non-ROMD memory ranges are now correctly mapped in Cameron Esfahani via
2019-11-21 22:54 ` [PATCH 2/5] hvf: remove TSC synchronization code because it isn't fully complete Cameron Esfahani via
2019-11-21 22:54 ` [PATCH 3/5] hvf: correctly handle REX prefix in relation to legacy prefixes Cameron Esfahani via
2019-11-21 22:54 ` [PATCH 4/5] hvf: more accurately match SDM when setting CR0 and PDPTE registers Cameron Esfahani via
2019-11-21 22:54 ` [PATCH 5/5] hvf: save away type as well as vector so we can reinject them Cameron Esfahani via
2019-11-22 0:02 ` [PATCH 0/5] hvf: stability fixes for HVF no-reply
2019-11-24 12:17 ` Lukas Straub [this message]
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=20191124131730.19ad6bf1@luklap \
--to=lukasstraub2@web.de \
--cc=dirty@apple.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 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.