All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robbie Dinn <robbie@microbus.com>
To: xen-devel@lists.xensource.com
Subject: Re: wget and Zope crashes on post-2.0.6 -testing
Date: Fri, 10 Jun 2005 20:52:02 +0100	[thread overview]
Message-ID: <42A9EF62.4050506@microbus.com> (raw)
In-Reply-To: <9c5e466efcd5d7dfb6487487187d2c3e@cl.cam.ac.uk>

Hi all

Keir Fraser wrote:
> 
> When set it causes a fault whenever the FPU is accessed. We use it to 
> lazily initialise the FPU for the currently running process. At 
> context-switch time we look at the process we are descheduling and, if 
> it hasn;t used the FPU in its time slice, we don;t save FPU state and we 
> don;t set the TS bit (because we assume it must be already set).
> 
> The last point is where we can fall down: if the TS bit in fact *isn;t* 
> set, then we are screwed for all time. The kernel will never realise a 
> process is using the FPU because we will never take the TS fault, 
> because the TS bit is clear. Thus state doesn;t get saved/restored 
> during context switch and the TS bit never gets set. So its a self 
> perpetuating state once you're in it.

I have an end user question rather than a developers Q.

Say I have an xen machine with several domains, some with kernels
that have the FPU bug fix and some without. Can a domain with
the buggy kernel upset a domain with a bug free kernel?
Or does this just affect processes within one domain?

I might want to be a bit more hasty in upgrading all the kernels
if a buggy kernel/domain can upset a good kernel/domain.

  reply	other threads:[~2005-06-10 19:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 21:19 RE: wget and Zope crashes on post-2.0.6 -testing Ian Pratt
2005-06-08 21:42 ` Kurt Garloff
2005-06-08 21:55   ` Keir Fraser
2005-06-10 19:52     ` Robbie Dinn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-10 20:01 Ian Pratt
2005-06-08 17:58 Ian Pratt
2005-06-02 14:32 Ian Pratt
2005-06-02 15:07 ` Osma Suominen
2005-06-03  9:04 ` Osma Suominen
2005-06-08 17:44   ` Keir Fraser
2005-06-02 13:50 Ian Pratt
2005-06-02 14:21 ` Osma Suominen
2005-06-02 10:22 Osma Suominen

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=42A9EF62.4050506@microbus.com \
    --to=robbie@microbus.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.