public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Dave Anderson <anderson@redhat.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: olaf@aepfle.de, xen-devel@lists.xensource.com,
	konrad wilk <konrad.wilk@oracle.com>,
	andrew cooper3 <andrew.cooper3@citrix.com>,
	ptesarik@suse.cz, duanshuidao@hotmail.com, jbeulich@suse.com,
	kexec@lists.infradead.org, crash-utility@redhat.com
Subject: Re: [PATCH 0/5] crash: Bundle of fixes for Xen
Date: Wed, 14 Nov 2012 14:52:00 -0500 (EST)	[thread overview]
Message-ID: <935158332.31770683.1352922720179.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20121113161000.GA2942@host-192-168-1-59.local.net-space.pl>



----- Original Message -----
> Hi,
> 
> Here is next bundle of fixes for crash Xen support:
>   - xen: Fix page tables caching issues,
>   - xen: Use init_tss array or per_cpu__init_tss,
>   - xen: Use per_cpu__crash_notes or crash_notes array,
>   - xen: Try hard to get max_cpus value,
>   - xen: Use cpu_present_map instead of cpu_online_map.
> 
> All patches were tested with Xen versions up to 4.2.
> 
> Daniel
> 

Hi Daniel,

The patches look reasonable to me, and they test OK on older
RHEL5 dom0 dumpfiles.  It would be interesting to see whether
they work for Hu Jun's SUSE kernel dumpfile.  I've cc'd him
directly.

Thanks,
  Dave

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2012-11-14 19:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 16:10 [PATCH 0/5] crash: Bundle of fixes for Xen Daniel Kiper
2012-11-14 19:52 ` Dave Anderson [this message]
2012-11-15  0:16   ` Jun Hu
  -- strict thread matches above, loose matches on Subject: below --
2012-11-15  9:29 Daniel Kiper

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=935158332.31770683.1352922720179.JavaMail.root@redhat.com \
    --to=anderson@redhat.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=crash-utility@redhat.com \
    --cc=daniel.kiper@oracle.com \
    --cc=duanshuidao@hotmail.com \
    --cc=jbeulich@suse.com \
    --cc=kexec@lists.infradead.org \
    --cc=konrad.wilk@oracle.com \
    --cc=olaf@aepfle.de \
    --cc=ptesarik@suse.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox