All of lore.kernel.org
 help / color / mirror / Atom feed
From: Glauber de Oliveira Costa <gcosta@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH/RFC] Wrong account for cpus other than 0 on hotplug
Date: Fri, 13 Oct 2006 18:18:50 -0300	[thread overview]
Message-ID: <20061013211850.GA14367@redhat.com> (raw)
In-Reply-To: <C155B6C1.2829%Keir.Fraser@cl.cam.ac.uk>

On Fri, Oct 13, 2006 at 09:33:53PM +0100, Keir Fraser wrote:
> On 13/10/06 6:50 pm, "Glauber de Oliveira Costa" <gcosta@redhat.com> wrote:
> 
> 
> This patch turns off the missing ticks accounting entirely, as the
> runstate_info structure will never be updated. Are you sure this appears to
> be an x86_64-specific issue?

That's why I was almost sure it was wrong, and was expecting comments
:-)
Among all machines we have, it just seem to be happening in a few of
them. Besides being x86_64, they're 8-way, which can be another sort of
problem.

I just found that the offending code is in the HV itself, and not in the
guest. In arch_do_vcpu_op(), we see that the information is only passed
up to the guest, if the check (current == v) holds, which seems to be
the
true source of it. (taking the check away makes it work).

I can see no reason for this check to be there. If there is one, we
could maybe make sure it holds. (maybe calling set_current(v) on HV
side?)

Your comments on this are , as usual, very welcome ;-)


-- 
Glauber de Oliveira Costa
Red Hat Inc.
"Free as in Freedom"

  reply	other threads:[~2006-10-13 21:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13 17:50 [PATCH/RFC] Wrong account for cpus other than 0 on hotplug Glauber de Oliveira Costa
2006-10-13 20:33 ` Keir Fraser
2006-10-13 21:18   ` Glauber de Oliveira Costa [this message]
2006-10-13 21:56     ` Keir Fraser

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=20061013211850.GA14367@redhat.com \
    --to=gcosta@redhat.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.