From: Sheng Yang <sheng@linux.intel.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [patch 2/2] QEMU/KVM: provide an option to disable in-kernel PIT int reinjection
Date: Tue, 30 Dec 2008 11:28:29 +0800 [thread overview]
Message-ID: <200812301128.29588.sheng@linux.intel.com> (raw)
In-Reply-To: <20081229174406.160714089@localhost.localdomain>
On Tuesday 30 December 2008 01:42:35 Marcelo Tosatti wrote:
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
>
>--
> #if defined(TARGET_I386) || defined(TARGET_X86_64) || defined(TARGET_IA64)
> || defined(__linux__) { "pcidevice", HAS_ARG, QEMU_OPTION_pcidevice },
> @@ -5267,6 +5270,11 @@ int main(int argc, char **argv, char **e
> kvm_pit = 0;
> break;
> }
> + case QEMU_OPTION_kvm_pit_no_reinject: {
> + extern int kvm_pit_no_reinject;
> + kvm_pit_no_reinject = 1;
> + break;
> + }
> case QEMU_OPTION_enable_nesting: {
> kvm_nested = 1;
> break;
Do we need check the conflict of --kvm-pit-no-reinject and --no-kvm-pit/--no-
kvm-irqchip? Check it ahead of kvm_qemu_create_context() seems a little
better...
--
regards
Yang, Sheng
next prev parent reply other threads:[~2008-12-30 3:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 17:42 [patch 0/2] QEMU/KVM: PIT no interrupt reinjection support Marcelo Tosatti
2008-12-29 17:42 ` [patch 1/2] libkvm: pit not reinject support Marcelo Tosatti
2008-12-30 10:09 ` Avi Kivity
2008-12-29 17:42 ` [patch 2/2] QEMU/KVM: provide an option to disable in-kernel PIT int reinjection Marcelo Tosatti
2008-12-30 3:28 ` Sheng Yang [this message]
2008-12-30 10:10 ` Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-12-30 17:48 [patch 0/2] QEMU/KVM: PIT interrupt reinjection control support (v2) Marcelo Tosatti
2008-12-30 17:48 ` [patch 2/2] QEMU/KVM: provide an option to disable in-kernel PIT int reinjection Marcelo Tosatti
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=200812301128.29588.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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 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.