From: Daniel Kiper <daniel.kiper@oracle.com>
To: hpa@zytor.com
Cc: xen-devel@lists.xensource.com, konrad.wilk@oracle.com,
andrew.cooper3@citrix.com, x86@kernel.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org, mingo@redhat.com,
ebiederm@xmission.com, jbeulich@suse.com,
maxim.uvarov@oracle.com, tglx@linutronix.de, vgoyal@redhat.com
Subject: Re: [PATCH v3 02/11] x86/kexec: Add extra pointers to transition page table PGD, PUD, PMD and PTE
Date: Thu, 27 Dec 2012 15:19:24 -0800 (PST) [thread overview]
Message-ID: <71b94237-c365-47ba-8d75-5ee1d8caee73@default> (raw)
> Hmm... this code is being redone at the moment... this might conflict.
Is this available somewhere? May I have a look at it?
Daniel
PS I am on holiday until 02/01/2013 and I could not
have access to my email box. Please be patient.
At worst case I will send reply when I will be
back at office.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2012-12-27 23:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 23:19 Daniel Kiper [this message]
2012-12-28 12:59 ` [PATCH v3 02/11] x86/kexec: Add extra pointers to transition page table PGD, PUD, PMD and PTE Borislav Petkov
2013-01-04 14:12 ` Daniel Kiper
-- strict thread matches above, loose matches on Subject: below --
2012-12-27 2:18 [PATCH v3 00/11] xen: Initial kexec/kdump implementation Daniel Kiper
2012-12-27 2:18 ` [PATCH v3 01/11] kexec: introduce kexec firmware support Daniel Kiper
2012-12-27 2:18 ` [PATCH v3 02/11] x86/kexec: Add extra pointers to transition page table PGD, PUD, PMD and PTE Daniel Kiper
2012-12-27 3:33 ` H. Peter Anvin
2013-01-03 9:34 ` Jan Beulich
2013-01-04 15:15 ` Daniel Kiper
2013-01-04 16:12 ` Jan Beulich
2013-01-04 17:25 ` Daniel Kiper
2013-01-07 9:48 ` Jan Beulich
2013-01-07 12:52 ` Daniel Kiper
2013-01-07 13:05 ` Jan Beulich
2013-01-09 18:42 ` 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=71b94237-c365-47ba-8d75-5ee1d8caee73@default \
--to=daniel.kiper@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=kexec@lists.infradead.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxim.uvarov@oracle.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--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