xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: tutu sky <ooohooo_u@hotmail.com>, xen devel <xen-devel@lists.xen.org>
Subject: Re: what will happen for a floated vcpu?
Date: Fri, 1 Apr 2016 16:18:34 +0200	[thread overview]
Message-ID: <1459520314.5082.275.camel@citrix.com> (raw)
In-Reply-To: <HE1PR05MB13087B9D1D275563F330E0FE8D990@HE1PR05MB1308.eurprd05.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 2386 bytes --]

On Thu, 2016-03-31 at 16:27 +0000, tutu sky wrote:
> Thanks Dario,
> Yeah, you are totally right, but software crashes are almost a result
> of hardware faults. 
>
Well, no, I'd sa that software crashes are almost always due to bugs in
the software itself. Then there are also hardware faults.

> I mean if a part of a core for example register file or maybe
> floating point unit or even ALU, suddenly stop working or does
> malfunction, what will happen for the corresponding vcpu which it is
> running? Does that vcpu crash (as a part of a software) or migrate to
> another core? 
>
I still don't follow. When you say "register file or ALU stop working
or malfunction", that does not mean much, unless better specify what
malfunction means.

For instance, if a CPU starts to behave in such a way that you store
0xabcd in register R1 and then, when you later read it, you read
0xdcba, what would happen? How does Xen (or any other hypervisor or OS)
knows this is a malfunctioning. Well, that entirely depend of what
specific piece of code is running when the malfunctioning manifests,
and what will likely happen is that the execution of the software would
be altered in a way that the software was not expecting and, at some
point, things will crash. Whether it would be the hypervisor to crash,
or the OS of a guest, or a user level process in a guest, is again
dependant on a lot of things.

So, really, to a question like "what happens to a Xen system if ALU
starts to malfunction?", the only possible answer is "bad things, but
who knows".

> You just please imagine recoverable faults. Has Xen any plan for deal
> with such a situation? 
>
The "situation" you're asking about is too broad a thing to have a plan
for it, as a whole.

For specific issues, there may or may not be plans or actually
implemented solution.

For examples (but I don't really know if this could be related to what
you're thinking about) there is this:
https://en.wikipedia.org/wiki/Machine-check_exception

And Xen does some MCE stuff (but I don't know the details myself).

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-04-01 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 20:06 what will happen for a floated vcpu? tutu sky
2016-03-31 16:00 ` Dario Faggioli
2016-03-31 16:27   ` tutu sky
2016-04-01 14:18     ` Dario Faggioli [this message]

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=1459520314.5082.275.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=ooohooo_u@hotmail.com \
    --cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).