From: Chao Peng <chao.p.peng@linux.intel.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Ian.Campbell@citrix.com, stefano.stabellini@eu.citrix.com,
Ian.Jackson@eu.citrix.com, xen-devel@lists.xen.org,
xumengpanda@gmail.com
Subject: Re: [PATCH for Xen 4.6 0/5] Several PSR fixes in libxl
Date: Tue, 29 Sep 2015 11:08:31 +0800 [thread overview]
Message-ID: <20150929030830.GG5813@pengc-linux.bj.intel.com> (raw)
In-Reply-To: <1443454945.3276.105.camel@citrix.com>
On Mon, Sep 28, 2015 at 05:42:25PM +0200, Dario Faggioli wrote:
> On Mon, 2015-09-28 at 15:16 +0100, Wei Liu wrote:
> > On Mon, Sep 28, 2015 at 07:54:48PM +0800, Chao Peng wrote:
> > > The patch basically contains several PSR fixes in libxl.
> > > patch1-3: fix the socket display error in certain hotplug case.
> > > patch4: fix a minor range check.
> > > patch5: improve the PSR document.
> > >
> > > Detailed problem and fix please see commit message.
> > >
> >
> > I've gone through all patches. This series looks sensible to me. And
> > I
> > see the point of getting in it for 4.6 to avoid releasing APIs that
> > are
> > deemed buggy.
> >
> FWIW, I totally agree.
>
> The patch looks sensible to me too, I've only found a couple of minor
> issues.
>
> > I would still like some more proof reading from someone who have
> > played
> > with this feature. I've CCed Dario and Meng.
> >
> Thanks for pinging... I've done my best. :-)
>
> About the suggestions I provided, the more important thing, IMO, is the
> name of the new function for retrieving the available sockets bitmap,
> which I really think it should be called libxl_get_online_socketmap().
>
> The others are indeed minor things, which don't affect public APIs and
> hence --although I'd prefer to see them addressed-- we can fix/change
> them post 4.6 too.
Thanks for the quick followup from you guys. I will send another version
to address these comments.
Chao
prev parent reply other threads:[~2015-09-29 3:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 11:54 [PATCH for Xen 4.6 0/5] Several PSR fixes in libxl Chao Peng
2015-09-28 11:54 ` [PATCH for Xen 4.6 1/5] tools/libxl: introduce libxl_socket_bitmap_fill Chao Peng
2015-09-28 14:12 ` Wei Liu
2015-09-28 14:53 ` Dario Faggioli
2015-09-28 14:57 ` Wei Liu
2015-09-29 2:47 ` Chao Peng
2015-09-29 2:49 ` Chao Peng
2015-09-28 11:54 ` [PATCH for Xen 4.6 2/5] tools/libxl: fix socket display error for CMT Chao Peng
2015-09-28 14:13 ` Wei Liu
2015-09-28 15:06 ` Dario Faggioli
2015-09-28 15:36 ` Wei Liu
2015-09-29 2:53 ` Chao Peng
2015-09-28 11:54 ` [PATCH for Xen 4.6 3/5] tools/libxl: return socket id from libxl_psr_cat_get_l3_info Chao Peng
2015-09-28 14:13 ` Wei Liu
2015-09-28 15:35 ` Dario Faggioli
2015-09-28 15:46 ` Wei Liu
2015-09-29 3:05 ` Chao Peng
2015-09-29 7:19 ` Dario Faggioli
2015-09-28 11:54 ` [PATCH for Xen 4.6 4/5] tools/libxl: fix range check in main_psr_cat_cbm_set Chao Peng
2015-09-28 14:14 ` Wei Liu
2015-09-28 15:16 ` Dario Faggioli
2015-09-28 11:54 ` [PATCH for Xen 4.6 5/5] docs: make xl-psr.markdown more precise Chao Peng
2015-09-28 14:14 ` Wei Liu
2015-09-28 15:15 ` Dario Faggioli
2015-09-28 14:16 ` [PATCH for Xen 4.6 0/5] Several PSR fixes in libxl Wei Liu
2015-09-28 15:42 ` Dario Faggioli
2015-09-29 3:08 ` Chao Peng [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=20150929030830.GG5813@pengc-linux.bj.intel.com \
--to=chao.p.peng@linux.intel.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=xumengpanda@gmail.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 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).