Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Young <dyoung@redhat.com>
To: Simon Horman <horms@verge.net.au>
Cc: kexec@lists.infradead.org
Subject: Re: [ANNOUNCE] kexec-tools 2.0.7
Date: Mon, 9 Jun 2014 10:15:37 +0800	[thread overview]
Message-ID: <20140609021537.GC1924@darkstar.nay.redhat.com> (raw)
In-Reply-To: <20140609010134.GA25776@verge.net.au>

On 06/09/14 at 10:01am, Simon Horman wrote:
> Hi all,
> 
> I am happy to announce the release of kexec-tools 2.0.7.

Simon,

Thanks for the new release.

FYI, the efi kernel patch has been merged into 3.15 kernel:
commit a3530e8fe980f756b823d451fe9243f26db95fa5
Author: Dave Young <dyoung@redhat.com>
Date:   Fri May 30 11:20:10 2014 +0800

    x86/efi: Do not export efi runtime map in case old map
    
    For ioremapped efi memory aka old_map the virt addresses are not persistant
    across kexec reboot. kexec-tools will read the runtime maps from sysfs then
    pass them to 2nd kernel and assuming kexec efi boot is ok. This will cause
    kexec boot failure.
    
    To address this issue do not export runtime maps in case efi old_map so
    userspace can use no efi boot instead.
    
    Signed-off-by: Dave Young <dyoung@redhat.com>
    Acked-by: Borislav Petkov <bp@suse.de>
    Acked-by: Vivek Goyal <vgoyal@redhat.com>
    Signed-off-by: Matt Fleming <matt.fleming@intel.com>

--
Thanks
Dave

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

  reply	other threads:[~2014-06-09  2:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09  1:01 [ANNOUNCE] kexec-tools 2.0.7 Simon Horman
2014-06-09  2:15 ` Dave Young [this message]
2014-06-09  3:11   ` Simon Horman
2014-06-09  9:54 ` WANG Chao
2014-06-09 20:41   ` Yegor Yefremov
2014-06-10  2:29     ` Simon Horman

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=20140609021537.GC1924@darkstar.nay.redhat.com \
    --to=dyoung@redhat.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.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