From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Beth Kon <eak@us.ibm.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 5/5] HPET interaction with in-kernel PIT (v6)
Date: Sun, 14 Jun 2009 12:18:24 +0300 [thread overview]
Message-ID: <4A34C060.8000100@redhat.com> (raw)
In-Reply-To: <4A34BE92.6010302@web.de>
Jan Kiszka wrote:
>>>
>>> struct kvm_pit_state {
>>> struct kvm_pit_channel_state channels[3];
>>> + u8 hpet_legacy_mode;
>>> };
>>>
>>>
>> This changes the ABI, breaking older binaries running on newer kernels,
>> or newer binaries running on older kernels.
>>
>
> As we have KVM_CREATE_PIT2 now, which includes struct kvm_pit_config
> with a lot of unused flags, it should be straightforward to negotiate
> the kvm_pit_state format between kernel and user space: kernel
> advertises support for the new one via capability, user space requests
> it via a bit in kvm_pit_state.flags.
>
We still need a new ioctl. The structure size is embedded in the ioctl
number, so any additions automatically cause version mismatches.
I sent patches some time ago to have the kernel automatically adjust for
this, but they weren't well received.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-14 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-12 1:46 [PATCH 1/5] Userspace changes for configuring irq0->inti2 override (v6) Beth Kon
2009-06-12 1:46 ` [PATCH 2/5] " Beth Kon
2009-06-12 1:46 ` [PATCH 3/5] BIOS changes for KVM HPET (v6) Beth Kon
2009-06-12 1:46 ` [PATCH 4/5] Userspace " Beth Kon
2009-06-14 8:55 ` Avi Kivity
2009-06-14 9:00 ` Avi Kivity
2009-06-12 1:46 ` [PATCH 5/5] HPET interaction with in-kernel PIT (v6) Beth Kon
2009-06-14 8:53 ` Avi Kivity
2009-06-14 9:10 ` Jan Kiszka
2009-06-14 9:18 ` Avi Kivity [this message]
2009-06-14 9:26 ` Jan Kiszka
2009-06-14 9:35 ` Avi Kivity
2009-06-14 8:50 ` [PATCH 1/5] Userspace changes for configuring irq0->inti2 override (v6) 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=4A34C060.8000100@redhat.com \
--to=avi@redhat.com \
--cc=eak@us.ibm.com \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.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.