From: Anthony Liguori <anthony@codemonkey.ws>
To: Gleb Natapov <gleb@qumranet.com>
Cc: Dor Laor <dor.laor@qumranet.com>,
kvm@vger.kernel.org, Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH 2/2] Remove -tdf
Date: Wed, 23 Jul 2008 10:31:08 -0500 [thread overview]
Message-ID: <48874EBC.1050209@codemonkey.ws> (raw)
In-Reply-To: <20080723055825.GA3196@minantech.com>
Gleb Natapov wrote:
> On Tue, Jul 22, 2008 at 08:20:41PM -0500, Anthony Liguori wrote:
>
>>> Currently both in-kernel PIT and even the in kernel irqchips are not
>>> 100% bullet proof.
>>> Of course this code is a hack, Gleb Natapov has send better fix for
>>> PIT/RTC to qemu list.
>>> Can you look into them:
>>> http://www.mail-archive.com/kvm@vger.kernel.org/msg01181.html
>>>
>> Paul Brook's initial feedback is still valid. It causes quite a lot of
>> churn and may not jive well with a virtual time base. An advantage to
>> the current -tdf patch is that it's more contained. I don't think
>> either approach is going to get past Paul in it's current form.
>>
> Yes, my patch causes a lot of churn because it changes widely used API.
>
Indeed.
> But the time drift fix itself is contained to PIT/RTC code only. The
> last patch series I've sent disables time drift fix if virtual time base
> is enabled as Paul requested. There was no further feedback from him.
>
I think there's a healthy amount of scepticism about whether tdf really
is worth it. This is why I suggested that we need to better quantify
exactly how much this patch set helps things. For instance, a time
drift test for kvm-autotest would be perfect.
tdf is ugly and deviates from how hardware works. A compelling case is
needed to justify it.
> As Jan Kiszka wrote in one of his mails may be Paul's virtual time base
> can be adopted to work with KVM too. BTW how virtual time base handles
> SMP guest?
>
I really don't know. I haven't looked to deeply at the virtual time
base. Keep in mind though, that QEMU SMP is not true SMP. All VCPUs
run in lock-step.
Regards,
Anthony Liguori
>> Also, it's important that this is reproducible in upstream QEMU and not
>> just in KVM. If we can make a compelling case for the importance of
>> this, we can possibly work out a compromise.
>>
>>
> I developed and tested my patch with upstream QEMU.
>
> --
> Gleb.
>
next prev parent reply other threads:[~2008-07-23 15:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 19:50 [PATCH 1/2] Fix bad merge Anthony Liguori
2008-07-22 19:50 ` [PATCH 2/2] Remove -tdf Anthony Liguori
2008-07-22 22:03 ` Dor Laor
2008-07-23 1:20 ` Anthony Liguori
2008-07-23 2:46 ` David S. Ahern
2008-07-23 5:58 ` Gleb Natapov
2008-07-23 15:31 ` Anthony Liguori [this message]
2008-07-24 22:55 ` Dor Laor
2008-07-27 9:38 ` Avi Kivity
2008-07-27 8:05 ` Avi Kivity
2008-07-27 8:02 ` [PATCH 1/2] Fix bad merge 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=48874EBC.1050209@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@qumranet.com \
--cc=dor.laor@qumranet.com \
--cc=gleb@qumranet.com \
--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.