xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Amit Tomer <amittomer25@gmail.com>
To: Julien Grall <julien@xen.org>
Cc: xen-devel@lists.xenproject.org,
	Stefano Stabellini <sstabellini@kernel.org>,
	Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
	Alejandro <alejandro.gonzalez.correo@gmail.com>,
	Andre Przywara <andre.przywara@arm.com>
Subject: Re: dom0 LInux 5.8-rc5 kernel failing to initialize cooling maps for Allwinner H6 SoC
Date: Fri, 24 Jul 2020 16:47:03 +0530	[thread overview]
Message-ID: <CABHD4K87aqCxsaW+j7uiM3kWQeHjSb+zQEs2p-SuYu83V-g38Q@mail.gmail.com> (raw)
In-Reply-To: <1c5cee83-295e-cc02-d018-b53ddc6e3590@xen.org>

Hi,

> I remember this discussion. The problem was that the PMU is using
> per-CPU interrupts. Xen is not yet able to handle PPIs as they often
> requires more context to be saved/restored (in this case the PMU context).
>
> There was a proposal to look if a device is using PPIs and just remove
> them from the Device-Tree. Unfortunately, I haven't seen any official
> submission for this patch.

But we have this patch that remove devices using PPIs
http://xenbits.xen.org/gitweb/?p=xen.git;a=commit;h=9b1a31922ac066ef0dffe36ebd6a6ba016567d69

Thanks
-Amit


  reply	other threads:[~2020-07-24 11:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-20 14:53 dom0 LInux 5.8-rc5 kernel failing to initialize cooling maps for Allwinner H6 SoC Alejandro
2020-07-24 10:45 ` Julien Grall
2020-07-24 11:17   ` Amit Tomer [this message]
2020-07-24 11:18     ` Julien Grall
2020-07-24 11:20   ` Alejandro
2020-07-26 20:24     ` André Przywara
2020-07-28 10:39       ` Alejandro
2020-07-28 11:17         ` André Przywara
2020-07-28 18:14           ` Stefano Stabellini
2020-07-28 18:52             ` Christopher Clark
2020-07-29  0:18               ` André Przywara

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=CABHD4K87aqCxsaW+j7uiM3kWQeHjSb+zQEs2p-SuYu83V-g38Q@mail.gmail.com \
    --to=amittomer25@gmail.com \
    --cc=Volodymyr_Babchuk@epam.com \
    --cc=alejandro.gonzalez.correo@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=julien@xen.org \
    --cc=sstabellini@kernel.org \
    --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).