From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, sheng@linux.intel.com
Subject: Re: [patch 1/2] libkvm: pit not reinject support
Date: Wed, 31 Dec 2008 11:53:39 +0200 [thread overview]
Message-ID: <495B4123.8060705@redhat.com> (raw)
In-Reply-To: <20081230175034.215911602@localhost.localdomain>
Marcelo Tosatti wrote:
> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
>
> Index: kvm-userspace.pit/libkvm/libkvm-x86.c
> ===================================================================
> --- kvm-userspace.pit.orig/libkvm/libkvm-x86.c
> +++ kvm-userspace.pit/libkvm/libkvm-x86.c
> @@ -75,6 +75,23 @@ int kvm_create_pit(kvm_context_t kvm)
> return 0;
> }
>
> +int kvm_pit_reinject_control(kvm_context_t kvm, int reinject)
> +{
> +#ifdef KVM_CAP_PIT_REINJECT_CONTROL
> + int r;
> + struct kvm_pit_reinject_control control;
> +
> + control.reinject = reinject;
> +
> + r = ioctl(kvm->fd, KVM_CHECK_EXTENSION, KVM_CAP_PIT_REINJECT_CONTROL);
> + if (r > 0) {
> + r = ioctl(kvm->vm_fd, KVM_PIT_REINJECT_CONTROL, &control);
> + return r;
> + }
> +#endif
> + return -ENOSYS;
> +}
> +
>
I moved this to libkvm.c to avoid a link error on non-x86.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-12-31 9:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 17:48 [patch 0/2] QEMU/KVM: PIT interrupt reinjection control support (v2) Marcelo Tosatti
2008-12-30 17:48 ` [patch 1/2] libkvm: pit not reinject support Marcelo Tosatti
2008-12-31 9:53 ` Avi Kivity [this message]
2008-12-30 17:48 ` [patch 2/2] QEMU/KVM: provide an option to disable in-kernel PIT int reinjection Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
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
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=495B4123.8060705@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=sheng@linux.intel.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