From: Avi Kivity <avi@qumranet.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
Marcelo Tosatti <mtosatti@redhat.com>,
Chris Wright <chrisw@redhat.com>,
Glauber Costa <gcosta@redhat.com>,
kvm@vger.kernel.org, john stultz <johnstul@us.ibm.com>
Subject: Re: [patch 01/12] expose ACPI pmtimer to userspace (/dev/pmtimer)
Date: Wed, 04 Jun 2008 13:35:46 +0300 [thread overview]
Message-ID: <48467002.9000002@qumranet.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0806041200150.3235@apollo.tec.linutronix.de>
Thomas Gleixner wrote:
> On Wed, 4 Jun 2008, Avi Kivity wrote:
>
>> Anthony Liguori wrote:
>>
>>> Thomas Gleixner wrote:
>>>
>>>> Can we please keep that code inside of drivers/clocksource/acpi_pm.c
>>>> without creating a new disconnected file in drivers/char ?
>>>>
>>>> Btw, depending on the use case we might as well have a sysfs entry for
>>>> that.
>>>>
>>> I think sysfs would actually make a lot of sense for this.
>>>
>>>
>> It's read many thousands of times per second. You don't want a
>> read()/sprintf()/atoi() sequence every time.
>>
>
> Eek, according to Andrea it's only used for migration purpose.
>
Oh, right. We also emulate pmtimer in qemu but it shouldn't need to
read the host pmtimer.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-06-04 10:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 22:22 [patch 00/12] fake ACPI C2 emulation v2 Marcelo Tosatti
2008-05-29 22:22 ` [patch 01/12] expose ACPI pmtimer to userspace (/dev/pmtimer) Marcelo Tosatti
2008-06-01 16:34 ` Thomas Gleixner
2008-06-01 16:56 ` Anthony Liguori
2008-06-04 9:53 ` Avi Kivity
2008-06-04 10:01 ` Thomas Gleixner
2008-06-04 10:35 ` Avi Kivity [this message]
2008-06-01 17:56 ` Marcelo Tosatti
2008-06-01 18:17 ` Thomas Gleixner
2008-06-02 16:43 ` John Stultz
2008-06-03 4:09 ` Marcelo Tosatti
2008-05-29 22:22 ` [patch 02/12] KVM: allow multiple IO bitmap pages, provide userspace interface Marcelo Tosatti
2008-05-29 22:22 ` [patch 03/12] KVM: allow userspace to open access to ACPI pmtimer Marcelo Tosatti
2008-05-29 22:22 ` [patch 04/12] KVM: move muldiv64 to x86.c, export Marcelo Tosatti
2008-05-29 22:22 ` [patch 05/12] KVM: in-kernel ACPI timer emulation Marcelo Tosatti
2008-05-29 22:22 ` [patch 06/12] QEMU/KVM: self-disabling C2 emulation Marcelo Tosatti
2008-05-29 22:22 ` [patch 07/12] libkvm: interface to KVM_SET_OPEN_IOPORT Marcelo Tosatti
2008-05-29 22:22 ` [patch 08/12] QEMU/KVM: non-virtualized ACPI PMTimer support Marcelo Tosatti
2008-05-29 22:22 ` [patch 09/12] libkvm: in-kernel ACPI pmtimer interface Marcelo Tosatti
2008-05-29 22:22 ` [patch 10/12] QEMU/KVM: add option to disable in-kernel pmtimer emulation Marcelo Tosatti
2008-05-29 22:23 ` [patch 11/12] libkvm: interface for pmtimer save/restore Marcelo Tosatti
2008-05-29 22:23 ` [patch 12/12] QEMU/KVM: in-kernel pmtimer save/restore support Marcelo Tosatti
2008-06-01 9:21 ` [patch 00/12] fake ACPI C2 emulation v2 Avi Kivity
2008-06-02 16:08 ` Marcelo Tosatti
2008-06-04 10:49 ` Avi Kivity
2008-06-05 3:12 ` Marcelo Tosatti
2008-06-05 7:56 ` 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=48467002.9000002@qumranet.com \
--to=avi@qumranet.com \
--cc=anthony@codemonkey.ws \
--cc=chrisw@redhat.com \
--cc=gcosta@redhat.com \
--cc=johnstul@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=tglx@linutronix.de \
/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