All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Uma Sharma <uma.sharma523@gmail.com>,
	xen-devel@lists.xen.org
Cc: dario.faggioli@citrix.com, keir@xen.org,
	George.Dunlap@citrix.com, jbeulich@suse.com
Subject: Re: [PATCH 1/2] x86: identifying the boot cpu
Date: Fri, 13 Mar 2015 19:06:54 +0000	[thread overview]
Message-ID: <5503354E.1070103@eu.citrix.com> (raw)
In-Reply-To: <5503296C.7000903@citrix.com>

On 03/13/2015 06:16 PM, Andrew Cooper wrote:
> Please use git-send-email and thread your patch series properly.  You
> are still submitting 3 independent emails.
> 
> On 13/03/15 18:07, Uma Sharma wrote:
>> Provide helpers to access the socket and core IDs, resulting from
>> identification phase.
>> Initialize socket and core ID to -1 i.e invalid instead of 0. Having
>> that field in all elements set to 0 would induce credit2 to think that
>> the pCPU have already been initialized, and that all are on socket 0
>> in case of credit2 socket scheduler and on core 0 in case of credit2
>> core scheduler.
>>
>> Signed-off-by: Uma Sharma <uma.sharma523@gmail.com>
> 
> You have not addressed the cpu onlining/offlining problem which Jan
> asked you about.
> 
> Furthermore, you don't make any justification as to why it is safe to
> change the defaults under all the other users of cpu_data.

That's because Dario said these were his patches and that he would be
doing the revision based on comments.

That said, Uma, if it was your intention not to actually suggest this be
accepted now, then you probably should have put "RFC" in the subject
line, and mentioned that this is a patch that Dario is going to work on
a replacement for, so that people know not to review it.

 -George

  reply	other threads:[~2015-03-13 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13 18:07 [PATCH 1/2] x86: identifying the boot cpu Uma Sharma
2015-03-13 18:16 ` Andrew Cooper
2015-03-13 19:06   ` George Dunlap [this message]
2015-03-16 12:38 ` Jan Beulich

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=5503354E.1070103@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=uma.sharma523@gmail.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 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.