From: Paolo Bonzini <pbonzini@redhat.com>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: Nadav Amit <namit@cs.technion.ac.il>,
Jan Kiszka <jan.kiszka@siemens.com>, Bandan Das <bsd@redhat.com>,
qemu-devel@nongnu.org, kvm list <kvm@vger.kernel.org>,
avi.kivity@gmail.com
Subject: Re: [Qemu-devel] [PATCH 2/2] target-i386: kvm: Disable KVM quirks
Date: Mon, 13 Apr 2015 16:36:04 +0200 [thread overview]
Message-ID: <552BD454.1050105@redhat.com> (raw)
In-Reply-To: <A2299E90-8DFA-49B7-884E-F90179D46BE5@gmail.com>
On 13/04/2015 16:33, Nadav Amit wrote:
>>> >> Of course…
>>> >> Do you want a v2 now, later (after 4.2), or would you change it yourself?
>> >
>> > Later, close to 4.2 but not necessarily after it.
> Anyhow, in that case the KVM patch is also wrong (not reporting
> KVM_CAP_DISABLE_QUIRKS is supported). I don’t want to spam, so I’ll run some
> tests and resubmit.
Don't worry, I've fixed that already.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: kvm list <kvm@vger.kernel.org>,
Nadav Amit <namit@cs.technion.ac.il>,
Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, Bandan Das <bsd@redhat.com>,
avi.kivity@gmail.com
Subject: Re: [Qemu-devel] [PATCH 2/2] target-i386: kvm: Disable KVM quirks
Date: Mon, 13 Apr 2015 16:36:04 +0200 [thread overview]
Message-ID: <552BD454.1050105@redhat.com> (raw)
In-Reply-To: <A2299E90-8DFA-49B7-884E-F90179D46BE5@gmail.com>
On 13/04/2015 16:33, Nadav Amit wrote:
>>> >> Of course…
>>> >> Do you want a v2 now, later (after 4.2), or would you change it yourself?
>> >
>> > Later, close to 4.2 but not necessarily after it.
> Anyhow, in that case the KVM patch is also wrong (not reporting
> KVM_CAP_DISABLE_QUIRKS is supported). I don’t want to spam, so I’ll run some
> tests and resubmit.
Don't worry, I've fixed that already.
Paolo
next prev parent reply other threads:[~2015-04-13 14:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 23:32 [Qemu-devel][PATCH 0/2] target-i386: disable LINT0 after reset and init Nadav Amit
2015-04-12 23:32 ` [Qemu-devel] [PATCH " Nadav Amit
2015-04-12 23:32 ` [Qemu-devel][PATCH 1/2] target-i386: disable LINT0 after reset Nadav Amit
2015-04-12 23:32 ` [Qemu-devel] [PATCH " Nadav Amit
2015-04-13 14:12 ` [Qemu-devel][PATCH " Paolo Bonzini
2015-04-13 14:12 ` [Qemu-devel] [PATCH " Paolo Bonzini
2015-09-15 21:19 ` Alex Williamson
2015-09-15 21:19 ` Alex Williamson
2015-09-16 5:23 ` Jan Kiszka
2015-09-16 5:23 ` Jan Kiszka
2015-09-16 6:22 ` Nadav Amit
2015-09-16 6:22 ` [Qemu-devel] " Nadav Amit
2015-09-16 6:47 ` Gerd Hoffmann
2015-09-16 6:47 ` Gerd Hoffmann
2015-09-16 12:52 ` Nadav Amit
2015-09-16 12:52 ` Nadav Amit
2015-04-12 23:32 ` [Qemu-devel][PATCH 2/2] target-i386: kvm: Disable KVM quirks Nadav Amit
2015-04-12 23:32 ` [Qemu-devel] [PATCH " Nadav Amit
2015-04-13 14:13 ` [Qemu-devel][PATCH " Paolo Bonzini
2015-04-13 14:13 ` [Qemu-devel] [PATCH " Paolo Bonzini
2015-04-13 14:17 ` Nadav Amit
2015-04-13 14:17 ` Nadav Amit
2015-04-13 14:24 ` Paolo Bonzini
2015-04-13 14:24 ` Paolo Bonzini
2015-04-13 14:33 ` Nadav Amit
2015-04-13 14:33 ` Nadav Amit
2015-04-13 14:36 ` Paolo Bonzini [this message]
2015-04-13 14:36 ` 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=552BD454.1050105@redhat.com \
--to=pbonzini@redhat.com \
--cc=avi.kivity@gmail.com \
--cc=bsd@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=nadav.amit@gmail.com \
--cc=namit@cs.technion.ac.il \
--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.