From: Joanna Rutkowska <joanna@invisiblethingslab.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: A clocksource question
Date: Tue, 09 Mar 2010 12:06:57 +0100 [thread overview]
Message-ID: <4B962BD1.3060307@invisiblethingslab.com> (raw)
In-Reply-To: <4B9628F3.5060101@invisiblethingslab.com>
[-- Attachment #1.1: Type: text/plain, Size: 933 bytes --]
On 03/09/2010 11:54 AM, Joanna Rutkowska wrote:
> On 03/09/2010 11:50 AM, Keir Fraser wrote:
>> On 09/03/2010 10:47, "Joanna Rutkowska" <joanna@invisiblethingslab.com>
>> wrote:
>>
>>> Interestingly the above problem didn't seem to affect the Dom0 kernel
>>> based on xen/stable-2.6.32. Unfortunately I assume I'm no longer able to
>>> run this kernel when using Xen 3.4.2.
>>
>> You could run the 3.4.3 release candidates?
>>
> Let's just say that after my recent experience with a 4.0.0 release
> candidate, I decided to use a stable version (or at least for the
> hypervisor) for now :) I really want to use on a production system.
>
> Perhaps you would say that in that case I should not be using a pvops0
> kernel at all? But what would be a good alternative with all reasonable
> hardware support then?
>
...plus the xen/stable-2.6/.32 doesn't have the pciback, which I happen
to need in Dom0...
j.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 226 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-03-09 11:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 10:47 A clocksource question Joanna Rutkowska
2010-03-09 10:50 ` Keir Fraser
2010-03-09 10:54 ` Joanna Rutkowska
2010-03-09 11:06 ` Joanna Rutkowska [this message]
2010-03-09 12:07 ` Pasi Kärkkäinen
2010-03-09 12:10 ` Joanna Rutkowska
2010-03-09 15:42 ` Konrad Rzeszutek Wilk
2010-03-09 23:36 ` Jeremy Fitzhardinge
2010-03-10 22:13 ` Joanna Rutkowska
2010-03-11 0:07 ` Dan Magenheimer
2010-03-11 0:15 ` Joanna Rutkowska
2010-03-11 0:21 ` Ian Pratt
2010-03-11 0:44 ` Dan Magenheimer
2010-03-12 0:34 ` Joanna Rutkowska
2010-03-11 0:52 ` Joanna Rutkowska
2010-03-11 1:06 ` Jeremy Fitzhardinge
2010-03-11 1:19 ` Joanna Rutkowska
2010-03-11 4:55 ` Jeremy Fitzhardinge
2010-03-11 10:49 ` Joanna Rutkowska
2010-03-12 0:27 ` Joanna Rutkowska
2010-03-12 0:49 ` Jeremy Fitzhardinge
2010-03-12 0:38 ` Joanna Rutkowska
2010-03-12 19:02 ` Joanna Rutkowska
2010-03-12 21:24 ` Jeremy Fitzhardinge
2010-03-12 21:56 ` Tobias Geiger
2010-03-12 22:02 ` Jeremy Fitzhardinge
2010-03-12 21:01 ` Joanna Rutkowska
2010-03-12 21:13 ` Joanna Rutkowska
2010-03-12 23:48 ` Jeremy Fitzhardinge
2010-03-13 9:58 ` Joanna Rutkowska
2010-03-13 19:30 ` Jeremy Fitzhardinge
2010-03-15 6:49 ` Tobias Geiger
2010-03-16 6:01 ` Joanna Rutkowska
2010-03-17 13:35 ` Tobias Geiger
2010-03-17 15:21 ` Joanna Rutkowska
2010-03-17 16:20 ` Jeremy Fitzhardinge
2010-03-17 17:05 ` Joanna Rutkowska
2010-03-17 17:21 ` Jeremy Fitzhardinge
2010-03-17 16:26 ` Dan Magenheimer
2010-03-12 22:56 ` Tobias Geiger
2010-03-11 7:47 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2010-03-12 11:42 Tobias Geiger
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=4B962BD1.3060307@invisiblethingslab.com \
--to=joanna@invisiblethingslab.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.