From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Juergen Gross <juergen.gross@ts.fujitsu.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: per_cpu problem
Date: Tue, 29 Dec 2009 15:01:38 +0000 [thread overview]
Message-ID: <C75FCA52.5406%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B3A02A8.2030407@ts.fujitsu.com>
On 29/12/2009 13:22, "Juergen Gross" <juergen.gross@ts.fujitsu.com> wrote:
> Who is copying cpu0 data to cpu1???
> If this isn't a bug but a feature, I suspect the following in schedule.c is
> working only by luck:
It's a feature, kicking in too late. I'll fix this up for you.
-- Keir
next prev parent reply other threads:[~2009-12-29 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 12:45 per_cpu problem Juergen Gross
2009-12-29 13:22 ` Juergen Gross
2009-12-29 15:01 ` Keir Fraser [this message]
2009-12-29 15:13 ` 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=C75FCA52.5406%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=juergen.gross@ts.fujitsu.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.