From: Paolo Bonzini <pbonzini@redhat.com>
To: Roman Bolshakov <r.bolshakov@yadro.com>,
Sukrit Bhatnagar <skrtbhtngr@gmail.com>
Cc: qemu-devel@nongnu.org, Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH RESEND v2 2/2] cpus: move hvf_cpu_synchronize* calls to cpu_synchronize* functions
Date: Wed, 10 Apr 2019 19:10:51 +0200 [thread overview]
Message-ID: <ed7dd764-ff54-58a3-b4b4-ed6951da6ef6@redhat.com> (raw)
In-Reply-To: <20190410140244.l5viavfey2ymzw6k@SPB-NB-133.local>
On 10/04/19 16:02, Roman Bolshakov wrote:
> I've applied, built and tested both sequentially. Applying and running
> with patch 1/2 alone doesn't result in the behavior I mentioned. I also
> tried to apply only the first hunk that moves hvf_cpu_synchronize_state
> into cpu_synchronize_state and it also causes the issue with BIOS.
>
> Honestly, I don't know if the tests run qemu with hvf accel. AFAIK
> kvm-unit-tests can be used to test an accel itself.
No, tests do not cover HVF.
Paolo
next prev parent reply other threads:[~2019-04-10 17:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 11:58 [Qemu-devel] [PATCH RESEND v2 0/2] Move hvf_cpu_synchronize* calls to cpu_synchronize* functions Sukrit Bhatnagar
2019-04-07 11:58 ` Sukrit Bhatnagar
2019-04-07 11:58 ` [Qemu-devel] [PATCH RESEND v2 1/2] hvf: declare hvf_handle_io if NEED_CPU_H is defined Sukrit Bhatnagar
2019-04-07 11:58 ` Sukrit Bhatnagar
2019-04-10 11:40 ` Roman Bolshakov
2019-04-10 11:40 ` Roman Bolshakov
2019-04-07 11:58 ` [Qemu-devel] [PATCH RESEND v2 2/2] cpus: move hvf_cpu_synchronize* calls to cpu_synchronize* functions Sukrit Bhatnagar
2019-04-07 11:58 ` Sukrit Bhatnagar
2019-04-10 11:50 ` Roman Bolshakov
2019-04-10 11:50 ` Roman Bolshakov
2019-04-10 12:05 ` Sukrit Bhatnagar
2019-04-10 12:05 ` Sukrit Bhatnagar
2019-04-10 14:02 ` Roman Bolshakov
2019-04-10 14:02 ` Roman Bolshakov
2019-04-10 17:10 ` Paolo Bonzini [this message]
2019-04-10 17:10 ` Paolo Bonzini
2019-04-07 12:05 ` [Qemu-devel] [PATCH RESEND v2 0/2] Move " Sukrit Bhatnagar
2019-04-07 12:05 ` Sukrit Bhatnagar
2019-04-09 8:28 ` Marcel Apfelbaum
2019-04-09 8:28 ` Marcel Apfelbaum
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=ed7dd764-ff54-58a3-b4b4-ed6951da6ef6@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.com \
--cc=rth@twiddle.net \
--cc=skrtbhtngr@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).