From: Jan Kiszka <jan.kiszka@web.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] kvm: fix Win2k boot without KVM
Date: Sat, 03 Nov 2012 19:51:42 +0100 [thread overview]
Message-ID: <509567BE.9000306@web.de> (raw)
In-Reply-To: <e188193e51fb42f2ff65cdd33faba568d557ea66.1351968543.git.blauwirbel@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On 2012-11-03 19:49, Blue Swirl wrote:
> Ignore accesses to VAPIC when kvmvapic is not enabled.
>
> Cc: Jan Kiszka <jan.kiszka@web.de>
> Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
> ---
> hw/kvmvapic.c | 7 ++++---
> 1 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/hw/kvmvapic.c b/hw/kvmvapic.c
> index dc111ee..a97d532 100644
> --- a/hw/kvmvapic.c
> +++ b/hw/kvmvapic.c
> @@ -612,6 +612,9 @@ static void vapic_write(void *opaque, hwaddr addr, uint64_t data,
> hwaddr rom_paddr;
> VAPICROMState *s = opaque;
>
> + if (!kvm_irqchip_in_kernel()) {
> + return;
> + }
> cpu_synchronize_state(env);
>
> /*
> @@ -665,9 +668,7 @@ static void vapic_write(void *opaque, hwaddr addr, uint64_t data,
> break;
> default:
> case 4:
> - if (!kvm_irqchip_in_kernel()) {
> - apic_poll_irq(env->apic_state);
> - }
> + apic_poll_irq(env->apic_state);
> break;
> }
> }
>
NACK, I'm already debugging the true reason (related to code patching).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2012-11-03 18:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-03 18:49 [Qemu-devel] [PATCH] kvm: fix Win2k boot without KVM Blue Swirl
2012-11-03 18:51 ` Jan Kiszka [this message]
2012-11-03 18:56 ` Blue Swirl
2012-11-03 19:03 ` Jan Kiszka
2012-11-03 19:10 ` Blue Swirl
2012-11-03 19:10 ` Jan Kiszka
2012-11-03 19:26 ` Blue Swirl
2012-11-03 19:37 ` Jan Kiszka
2012-11-03 20:57 ` Jan Kiszka
2012-11-03 21:00 ` Jan Kiszka
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=509567BE.9000306@web.de \
--to=jan.kiszka@web.de \
--cc=blauwirbel@gmail.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).