From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: "qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Alexander Graf" <agraf@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Andreas Färber" <andreas.faerber@web.de>,
"Avi Kivity" <avi@redhat.com>
Subject: Re: [Qemu-trivial] [PATCH] Use SIGIO with caution
Date: Tue, 31 May 2011 18:19:55 -0500 [thread overview]
Message-ID: <4DE5779B.4070304@codemonkey.ws> (raw)
In-Reply-To: <4DE560F1.70407@web.de>
On 05/31/2011 04:43 PM, Jan Kiszka wrote:
> On 2011-05-31 23:11, Andreas Färber wrote:
>> Am 31.05.2011 um 21:49 schrieb Anthony Liguori:
>>> At one point in time, it was the only way to get a high res clock.
>>> Now, it Just Works provided you don't have an ancient kernel.
>>
>> I'm curious, what's ancient these days? 2.6.29 or more like 2.4.x?
>
> IIRC, highres timers started to work around 2.6.24 on x86. Anyone on
> such an old kernel is likely also not interested in updating QEMU.
Yeah, 2.6.24 is ancient now that we're in the 3.0 world ;-)
Regards,
Anthony Liguori
>
> Jan
>
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: "qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Alexander Graf" <agraf@suse.de>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Andreas Färber" <andreas.faerber@web.de>,
"Avi Kivity" <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Use SIGIO with caution
Date: Tue, 31 May 2011 18:19:55 -0500 [thread overview]
Message-ID: <4DE5779B.4070304@codemonkey.ws> (raw)
In-Reply-To: <4DE560F1.70407@web.de>
On 05/31/2011 04:43 PM, Jan Kiszka wrote:
> On 2011-05-31 23:11, Andreas Färber wrote:
>> Am 31.05.2011 um 21:49 schrieb Anthony Liguori:
>>> At one point in time, it was the only way to get a high res clock.
>>> Now, it Just Works provided you don't have an ancient kernel.
>>
>> I'm curious, what's ancient these days? 2.6.29 or more like 2.4.x?
>
> IIRC, highres timers started to work around 2.6.24 on x86. Anyone on
> such an old kernel is likely also not interested in updating QEMU.
Yeah, 2.6.24 is ancient now that we're in the 3.0 world ;-)
Regards,
Anthony Liguori
>
> Jan
>
next prev parent reply other threads:[~2011-05-31 23:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 21:50 [Qemu-trivial] [PATCH] Use SIGIO with caution Andreas Färber
2011-05-29 21:50 ` [Qemu-devel] " Andreas Färber
2011-05-31 13:47 ` [Qemu-trivial] " Anthony Liguori
2011-05-31 13:47 ` Anthony Liguori
2011-05-31 14:06 ` [Qemu-trivial] " Jan Kiszka
2011-05-31 14:06 ` Jan Kiszka
2011-05-31 14:26 ` [Qemu-trivial] " Anthony Liguori
2011-05-31 14:26 ` Anthony Liguori
2011-05-31 14:54 ` [Qemu-trivial] " Jan Kiszka
2011-05-31 14:54 ` Jan Kiszka
2011-05-31 15:44 ` [Qemu-trivial] " Alexander Graf
2011-05-31 15:44 ` Alexander Graf
2011-05-31 15:48 ` [Qemu-trivial] " Anthony Liguori
2011-05-31 15:48 ` Anthony Liguori
2011-05-31 16:16 ` [Qemu-trivial] " Alexander Graf
2011-05-31 16:16 ` Alexander Graf
2011-05-31 19:49 ` [Qemu-trivial] " Anthony Liguori
2011-05-31 19:49 ` Anthony Liguori
2011-05-31 21:11 ` [Qemu-trivial] " Andreas Färber
2011-05-31 21:11 ` Andreas Färber
2011-05-31 21:43 ` [Qemu-trivial] " Jan Kiszka
2011-05-31 21:43 ` [Qemu-devel] " Jan Kiszka
2011-05-31 23:19 ` Anthony Liguori [this message]
2011-05-31 23:19 ` Anthony Liguori
2011-05-31 14:11 ` [Qemu-trivial] " Avi Kivity
2011-05-31 14:11 ` Avi Kivity
2011-05-31 21:24 ` [Qemu-trivial] " Andreas Färber
2011-05-31 21:24 ` Andreas Färber
2011-06-01 22:30 ` [Qemu-trivial] " Stefan Hajnoczi
2011-06-01 22:30 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
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=4DE5779B.4070304@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=andreas.faerber@web.de \
--cc=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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.