xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Lan Tianyu <tianyu.lan@intel.com>
Cc: sstabellini@kernel.org, wei.liu2@citrix.com,
	George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
	ian.jackson@eu.citrix.com, Jan Beulich <JBeulich@suse.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 0/2] Xen: Fix Xen hypervisor panic during dumping timer info on huge machine.
Date: Wed, 12 Oct 2016 10:48:02 +0100	[thread overview]
Message-ID: <20161012094802.GK3687@citrix.com> (raw)
In-Reply-To: <b200cbff-ba70-3454-20f4-fa61533a1cb9@intel.com>

On Wed, Oct 12, 2016 at 04:20:02PM +0800, Lan Tianyu wrote:
> On 2016年10月12日 16:09, Jan Beulich wrote:
> >>>> On 12.10.16 at 17:44, <tianyu.lan@intel.com> wrote:
> >> This patchset is to fix triggering NMI watchdog during dump timer info
> >> on the huge machine with a mount of physical cpus. Detail please see
> >> change log of Patch 1.
> >>
> >> Previous discussion:
> >> https://patchwork.kernel.org/patch/9328449/ 
> >>
> >> Change since V1:
> >>         Add "async" param for handle_keypress() to identify
> >> whether run nonirq keyhandler in tasklet or not. This is to
> >> avoid processing debugkey sysctl asynchronously.
> >>
> >>
> >> Lan Tianyu (2):
> >>   Xen/Keyhandler: Rework process of nonirq keyhandler
> >>   Xen/timer: Process softirq during dumping timer info
> > 
> > This second patch went in already a few days ago.
> > 
> 
> Oh. Sorry for noise. I didn't notice that.
> 

It is always good practice to rebase your patch series on top of
staging, FWIW.

> > Also, any reason you send to the list twice (once @lists.xen.org,
> > and another time to @lists.xenproject.org)?
> 
> Sometime I found my patches wasn't able to arrive xen-devel and so
> send to both xen.org and xenproject.org maillist. I will double check.
> 

Both addresses should work. There are glitches from time to time though.
So do report to us if this happens again.

Wei.

> > 
> > Jan
> > 
> 
> 
> -- 
> Best regards
> Tianyu Lan

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

  reply	other threads:[~2016-10-12  9:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1476287051-17629-1-git-send-email-tianyu.lan@intel.com>
2016-10-12  8:09 ` [PATCH v2 0/2] Xen: Fix Xen hypervisor panic during dumping timer info on huge machine Jan Beulich
2016-10-12  8:20   ` Lan Tianyu
2016-10-12  9:48     ` Wei Liu [this message]
2016-10-12 11:08       ` Ian Jackson
2016-10-12 14:32         ` Lan, Tianyu
2016-10-12  7:58 Lan Tianyu

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=20161012094802.GK3687@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=tianyu.lan@intel.com \
    --cc=xen-devel@lists.xenproject.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).