From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH uq/master] kvm: Drop unused kvm_pit_in_kernel
Date: Thu, 22 Mar 2012 14:27:37 +0100 [thread overview]
Message-ID: <4F6B28C9.9090408@siemens.com> (raw)
In-Reply-To: <20120322125236.GG22368@redhat.com>
On 2012-03-22 13:52, Gleb Natapov wrote:
> On Thu, Mar 22, 2012 at 01:41:18PM +0100, Jan Kiszka wrote:
>> On 2012-03-22 08:18, Gleb Natapov wrote:
>>> On Wed, Mar 21, 2012 at 02:49:09PM +0100, Jan Kiszka wrote:
>>>> On 2012-03-21 14:41, Gleb Natapov wrote:
>>>>> On Wed, Mar 21, 2012 at 02:39:47PM +0100, Jan Kiszka wrote:
>>>>>> On 2012-03-21 14:36, Avi Kivity wrote:
>>>>>>> On 03/21/2012 02:36 PM, Jan Kiszka wrote:
>>>>>>>> This is now implied by kvm_irqchip_in_kernel.
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> So we can't have -no-kvm-pit?
>>>>>>>
>>>>>>> No huge loss, but unexpected.
>>>>>>
>>>>>> See e81dda195556e72f8cd294998296c1051aab30a8.
>>>>>>
>>>>> I am curious what is the reason for upstream to not supporting disabling the
>>>>> in-kernel PIT separately?
>>>>
>>>> It was considered no longer relevant:
>>>> http://thread.gmane.org/gmane.comp.emulators.kvm.devel/85393
>>>>
>>> Hmm, may be we should think about this some more. If in the (not so far)
>>> future we want to drop pit emulation from the kernel we may want to support
>>> -no-kvm-pit to allow migration from old kernels to new one.
>>
>> That's not an issue. Both device models are compatible, and you can
>> migrate between kernel_irqchip=on/off theses days with QEMU.
>>
> Cool. Including PIT lost tick compensation?
The feature is not yet available for the userspace PIT (we only support
tick compensation for the userspace RTC - IIRC). Requires better IRQ
injection feedback, you likely remember. ;)
Also, I wonder if the kernel exports all tick-compensation related
states for save/restore. Need to check again...
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Avi Kivity <avi@redhat.com>, kvm <kvm@vger.kernel.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH uq/master] kvm: Drop unused kvm_pit_in_kernel
Date: Thu, 22 Mar 2012 14:27:37 +0100 [thread overview]
Message-ID: <4F6B28C9.9090408@siemens.com> (raw)
In-Reply-To: <20120322125236.GG22368@redhat.com>
On 2012-03-22 13:52, Gleb Natapov wrote:
> On Thu, Mar 22, 2012 at 01:41:18PM +0100, Jan Kiszka wrote:
>> On 2012-03-22 08:18, Gleb Natapov wrote:
>>> On Wed, Mar 21, 2012 at 02:49:09PM +0100, Jan Kiszka wrote:
>>>> On 2012-03-21 14:41, Gleb Natapov wrote:
>>>>> On Wed, Mar 21, 2012 at 02:39:47PM +0100, Jan Kiszka wrote:
>>>>>> On 2012-03-21 14:36, Avi Kivity wrote:
>>>>>>> On 03/21/2012 02:36 PM, Jan Kiszka wrote:
>>>>>>>> This is now implied by kvm_irqchip_in_kernel.
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> So we can't have -no-kvm-pit?
>>>>>>>
>>>>>>> No huge loss, but unexpected.
>>>>>>
>>>>>> See e81dda195556e72f8cd294998296c1051aab30a8.
>>>>>>
>>>>> I am curious what is the reason for upstream to not supporting disabling the
>>>>> in-kernel PIT separately?
>>>>
>>>> It was considered no longer relevant:
>>>> http://thread.gmane.org/gmane.comp.emulators.kvm.devel/85393
>>>>
>>> Hmm, may be we should think about this some more. If in the (not so far)
>>> future we want to drop pit emulation from the kernel we may want to support
>>> -no-kvm-pit to allow migration from old kernels to new one.
>>
>> That's not an issue. Both device models are compatible, and you can
>> migrate between kernel_irqchip=on/off theses days with QEMU.
>>
> Cool. Including PIT lost tick compensation?
The feature is not yet available for the userspace PIT (we only support
tick compensation for the userspace RTC - IIRC). Requires better IRQ
injection feedback, you likely remember. ;)
Also, I wonder if the kernel exports all tick-compensation related
states for save/restore. Need to check again...
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-03-22 13:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 12:36 [PATCH uq/master] kvm: Drop unused kvm_pit_in_kernel Jan Kiszka
2012-03-21 12:36 ` [Qemu-devel] " Jan Kiszka
2012-03-21 13:36 ` Avi Kivity
2012-03-21 13:36 ` [Qemu-devel] " Avi Kivity
2012-03-21 13:39 ` Jan Kiszka
2012-03-21 13:39 ` [Qemu-devel] " Jan Kiszka
2012-03-21 13:41 ` Gleb Natapov
2012-03-21 13:41 ` [Qemu-devel] " Gleb Natapov
2012-03-21 13:49 ` Jan Kiszka
2012-03-21 13:49 ` [Qemu-devel] " Jan Kiszka
2012-03-22 7:18 ` Gleb Natapov
2012-03-22 7:18 ` [Qemu-devel] " Gleb Natapov
2012-03-22 12:41 ` Jan Kiszka
2012-03-22 12:41 ` [Qemu-devel] " Jan Kiszka
2012-03-22 12:52 ` Gleb Natapov
2012-03-22 12:52 ` [Qemu-devel] " Gleb Natapov
2012-03-22 13:27 ` Jan Kiszka [this message]
2012-03-22 13:27 ` Jan Kiszka
2012-03-27 10:48 ` Gleb Natapov
2012-03-27 10:48 ` [Qemu-devel] " Gleb Natapov
2012-03-21 23:00 ` [PATCH v2 " Jan Kiszka
2012-03-21 23:00 ` [Qemu-devel] " Jan Kiszka
2012-04-11 1:33 ` 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=4F6B28C9.9090408@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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 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.