linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Pavel Tatashin <pasha.tatashin@soleen.com>
Cc: sashal@kernel.org, mark.rutland@arm.com, vladimir.murzin@arm.com,
	kexec@lists.infradead.org, jmorris@namei.org,
	linux-kernel@vger.kernel.org, james.morse@arm.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 0/6] Allow kexec reboot for GICv3 and device tree
Date: Mon, 26 Aug 2019 20:13:13 +0100	[thread overview]
Message-ID: <20190826201313.246208e9@why> (raw)
In-Reply-To: <20190826190056.27854-1-pasha.tatashin@soleen.com>

On Mon, 26 Aug 2019 15:00:50 -0400
Pavel Tatashin <pasha.tatashin@soleen.com> wrote:

> Marc Zyngier added the support for kexec and GICv3 for EFI based systems.
> However, it is still not possible todo on systems with device trees.
> 
> Here is EFI fixes from Marc:
> https://lore.kernel.org/lkml/20180921195954.21574-1-marc.zyngier@arm.com
> 
> For Device Tree variant: lets allow reserve a memory region in interrupt
> controller node, and use this property to allocate interrupt tables.

There is no such thing as a "device tree variant". As long as your
bootloader implements EFI, everything will work correctly, whether
you're using DT, ACPI, or the anything else.

This already works today, without any need to add anything to the
kernel (I have systems using EDK II and u-boot, both implementing EFI,
and I'm able to kexec without any issue). If your bootloader doesn't
support EFI, here's a good opportunity to implement it!

Thanks,

	M.
-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-08-26 19:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-26 19:00 [PATCH v1 0/6] Allow kexec reboot for GICv3 and device tree Pavel Tatashin
2019-08-26 19:00 ` [PATCH v1 1/6] rqchip/gic-v3-its: reset prop table outside of allocation Pavel Tatashin
2019-08-26 19:00 ` [PATCH v1 2/6] rqchip/gic-v3-its: use temporary va / pa variables Pavel Tatashin
2019-08-26 19:00 ` [PATCH v1 3/6] rqchip/gic-v3-its: add reset pending table function Pavel Tatashin
2019-08-26 19:00 ` [PATCH v1 4/6] rqchip/gic-v3-its: move reset pending table outside of allocator Pavel Tatashin
2019-08-26 19:00 ` [PATCH v1 5/6] " Pavel Tatashin
2019-08-26 21:29   ` Pavel Tatashin
2019-08-26 19:00 ` [PATCH v1 6/6] dt-bindings: interrupt-controller: add optional memory-region Pavel Tatashin
2019-08-26 19:13 ` Marc Zyngier [this message]
2019-08-26 21:25   ` [PATCH v1 0/6] Allow kexec reboot for GICv3 and device tree Pavel Tatashin
2019-08-27  8:15     ` Marc Zyngier
2019-08-27  8:53       ` Pavel Tatashin
2019-08-27  9:24         ` Marc Zyngier

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=20190826201313.246208e9@why \
    --to=maz@kernel.org \
    --cc=james.morse@arm.com \
    --cc=jmorris@namei.org \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=sashal@kernel.org \
    --cc=vladimir.murzin@arm.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).