From: Roman Bolshakov <r.bolshakov@yadro.com>
To: <yaroshchuk2000@gmail.com>
Cc: qemu-trivial@nongnu.org, pbonzini@redhat.com,
qemu-devel@nongnu.org, dirty@apple.com
Subject: Re: [PATCH v3] target/i386/hvf: add vmware-cpuid-freq cpu feature
Date: Tue, 9 Feb 2021 13:32:34 +0300 [thread overview]
Message-ID: <YCJkwsLxtWuIwqU0@SPB-NB-133.local> (raw)
In-Reply-To: <20210122150518.3551-1-yaroshchuk2000@gmail.com>
On Fri, Jan 22, 2021 at 06:05:18PM +0300, yaroshchuk2000@gmail.com wrote:
> From: Vladislav Yaroshchuk <yaroshchuk2000@gmail.com>
>
> For `-accel hvf` cpu_x86_cpuid() is wrapped with hvf_cpu_x86_cpuid() to
> add paravirtualization cpuid leaf 0x40000010
> https://lkml.org/lkml/2008/10/1/246
>
> Leaf 0x40000010, Timing Information:
> EAX: (Virtual) TSC frequency in kHz.
> EBX: (Virtual) Bus (local apic timer) frequency in kHz.
> ECX, EDX: RESERVED (Per above, reserved fields are set to zero).
>
> On macOS TSC and APIC Bus frequencies can be readed by sysctl call with
> names `machdep.tsc.frequency` and `hw.busfrequency`
>
> This options is required for Darwin-XNU guest to be synchronized with
> host
>
> Leaf 0x40000000 not exposes HVF leaving hypervisor signature empty
>
> Signed-off-by: Vladislav Yaroshchuk <yaroshchuk2000@gmail.com>
> ---
> target/i386/hvf/hvf.c | 96 ++++++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 95 insertions(+), 1 deletion(-)
>
Queued, thanks!
-Roman
prev parent reply other threads:[~2021-02-09 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-13 20:52 [PATCH] target/i386/hvf: add vmware-cpuid-freq cpu feature yaroshchuk2000
2021-01-13 21:25 ` no-reply
2021-01-14 19:47 ` [PATCH v2] " yaroshchuk2000
2021-01-19 18:01 ` Roman Bolshakov
2021-01-19 18:14 ` Paolo Bonzini
2021-01-22 14:29 ` Vladislav Yaroshchuk
2021-01-19 22:37 ` dirty--- via
2021-01-22 14:51 ` Vladislav Yaroshchuk
2021-01-22 15:05 ` [PATCH v3] " yaroshchuk2000
2021-02-04 9:51 ` Roman Bolshakov
2021-02-09 10:32 ` Roman Bolshakov [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=YCJkwsLxtWuIwqU0@SPB-NB-133.local \
--to=r.bolshakov@yadro.com \
--cc=dirty@apple.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=yaroshchuk2000@gmail.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).