dle non xen specific hypercalls
Platforms that want to use SiP service could use platform
specific sip implementation.
Signed-off-by: Peng Fan
---
In my Dom0 kernel, there is SiP smccc call. Without xen, the call
will trap to ATF. With xen, I use hvccc to replace smccc, but
xen still report err
> Subject: Re: [PATCH V2] arm: xen: mm: use __GPF_DMA32 for arm64
>
> + Juergen, Boris
>
> On Fri, 30 Aug 2019, Christoph Hellwig wrote:
> > Can we take a step back and figure out what we want to do here?
> >
> > AFAICS this function allocates memory for the swiotlb-xen buffer, and
> > that means
From: Peng Fan
arm64 shares some code under arch/arm/xen, including mm.c.
However ZONE_DMA is removed by commit
ad67f5a6545("arm64: replace ZONE_DMA with ZONE_DMA32").
So add a check if CONFIG_ZONE_DMA32 is enabled use __GFP_DMA32.
Signed-off-by: Peng Fan
---
V3:
Use
el panic.
With this patch, vring_use_dma_api will return false, and
vring_map_one_sg will return sg_phys(sg) which is the correct phys
address in the predefined memory region.
vring_map_one_sg -> vring_use_dma_api
-> sg_phys(sg)
Signed-off-by: Peng Fan
---
drivers/virtio/virt
Hi
> -Original Message-
> From: h...@infradead.org [mailto:h...@infradead.org]
> Sent: 2019年1月21日 16:29
> To: Peng Fan
> Cc: m...@redhat.com; jasow...@redhat.com; sstabell...@kernel.org;
> h...@infradead.org; virtualizat...@lists.linux-foundation.org;
> xen-devel
unless we deactive the interrupt first.
So let's deactive the interrupts during GICv3 initialization to fix
this issue.
Signed-off-by: Peng Fan
---
xen/arch/arm/gic-v3.c | 4
1 file changed, 4 insertions(+)
diff --git a/xen/arch/arm/gic-v3.c b/xen/arch/arm/gic-v3.c
index 6fbc1
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 2019年1月23日 4:00
> To: Peng Fan
> Cc: m...@redhat.com; jasow...@redhat.com; sstabell...@kernel.org;
> h...@infradead.org; xen-devel@lists.xenproject.org;
> linux-remotep...@vger.
Hi stefano,
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 2019年1月24日 7:44
> To: h...@infradead.org
> Cc: Stefano Stabellini ; Peng Fan
> ; m...@redhat.com; jasow...@redhat.com;
> xen-devel@lists.xenproject.org; linux-remot
Hi Julien
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 2019年1月22日 18:55
> To: Peng Fan ; sstabell...@kernel.org
> Cc: xen-devel@lists.xenproject.org; Andre Przywara
>
> Subject: Re: [PATCH] arm: gic-v3: clear GICR active in
rupt will be in deactive state when
smp_call_function_interrupt.
Signed-off-by: Peng Fan
---
xen/arch/arm/gic.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/xen/arch/arm/gic.c b/xen/arch/arm/gic.c
index 6cc7dec706..300fdbd9ae 100644
--- a/xen/arch/arm/gic.c
+++ b/xen
Hi,
> -Original Message-
> From: h...@infradead.org [mailto:h...@infradead.org]
> Sent: 2019年1月24日 5:14
> To: Stefano Stabellini
> Cc: h...@infradead.org; Peng Fan ; m...@redhat.com;
> jasow...@redhat.com; xen-devel@lists.xenproject.org;
> linux-remotep...@vger.
> -Original Message-
> From: h...@infradead.org [mailto:h...@infradead.org]
> Sent: 2019年1月28日 16:00
> To: Peng Fan
> Cc: h...@infradead.org; Stefano Stabellini ;
> m...@redhat.com; jasow...@redhat.com; xen-devel@lists.xenproject.org;
> linux-remotep...@vger.
Hi Julien
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 2019年1月29日 23:57
> To: Peng Fan ; sstabell...@kernel.org; jgr...@suse.com
> Cc: xen-devel@lists.xenproject.org; Andre Przywara
>
> Subject: Re: [PATCH for-4.12] arm: gic: deact
Hi Julien
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 2019年1月30日 20:06
> To: Peng Fan ; sstabell...@kernel.org
> Cc: xen-devel@lists.xenproject.org; Andre Przywara
>
> Subject: Re: [PATCH] arm: gic-v3: clear GICR active interrupts
> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf
> Of Peng Fan
> Sent: 2019年1月30日 21:24
> To: Julien Grall ; sstabell...@kernel.org
> Cc: xen-devel@lists.xenproject.org; Andre Przywara
>
> Subject: Re: [Xen-de
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 2019年1月30日 21:49
> To: Peng Fan ; sstabell...@kernel.org
> Cc: xen-devel@lists.xenproject.org; Andre Przywara
>
> Subject: Re: [PATCH] arm: gic-v3: clear GICR active interrupts
>
>
cification, chapter
"8.11.3 GICR_ICACTIVER0, Interrupt Clear-Active Register 0", the RW
field of GICR_ICACTIVER0 resets to a value that is architecturally UNKNOWN.
So set a fixed value during gic-v3 initialization to make sure
interrupts are in deactivated state.
Signed-off-by: Peng Fa
Hi Julien
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 2019年2月1日 18:41
> To: Peng Fan ; sstabell...@kernel.org; jgr...@suse.com
> Cc: xen-devel@lists.xenproject.org
> Subject: Re: [PATCH for-4.12 v2] arm: gic-v3: deactiv
m.c.
> > However ZONE_DMA is removed by commit
> > ad67f5a6545("arm64: replace ZONE_DMA with ZONE_DMA32").
> > So to ARM64, need use __GFP_DMA32.
> >
> > Signed-off-by: Peng Fan
> > ---
> > arch/arm/xen/mm.c | 2 +-
> > 1 file change
Hi Robin,
> Subject: Re: [PATCH] arm: xen: mm: use __GPF_DMA32 for arm64
>
> On 09/07/2019 09:22, Peng Fan wrote:
> > arm64 shares some code under arch/arm/xen, including mm.c.
> > However ZONE_DMA is removed by commit
> > ad67f5a6545("arm64: replace ZONE_DMA wi
Hi Stefano,
> Subject: RE: [PATCH] arm: xen: mm: use __GPF_DMA32 for arm64
>
> On Wed, 28 Aug 2019, Peng Fan wrote:
> > Hi Robin,
> >
> > > Subject: Re: [PATCH] arm: xen: mm: use __GPF_DMA32 for arm64
> > >
> > > On 09/07/2019 09:22, Peng Fan wrot
From: Peng Fan
arm64 shares some code under arch/arm/xen, including mm.c.
However ZONE_DMA is removed by commit
ad67f5a6545("arm64: replace ZONE_DMA with ZONE_DMA32").
So introduce xen_set_gfp_dma for arm32/arm64 and using __GFP_DMA
for the former and __GFP_DMA32 for the latter.
Sig
cification, chapter
"8.11.3 GICR_ICACTIVER0, Interrupt Clear-Active Register 0", the RW
field of GICR_ICACTIVER0 resets to a value that is architecturally UNKNOWN.
So make sure all interrupts are deactivated at during initialization by
clearing the state.
Signed-off-by: Peng Fan
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 2019年2月3日 0:04
> To: Peng Fan ; sstabell...@kernel.org; jgr...@suse.com
> Cc: xen-devel@lists.xenproject.org
> Subject: Re: [PATCH for-4.12 v2] arm: gic-v3: deactivate SGI/PPI durin
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 2019年2月6日 5:39
> To: xen-devel@lists.xenproject.org
> Cc: sstabell...@kernel.org; Stefano Stabellini ;
> julien.gr...@arm.com; Peng Fan ; jgr...@suse.com
> Subject: [PATCH for-
memory
region. we do not have SoC support such large DRAM now, but we might
have in future.
Add BUG() to let people be aware of this issue.
Signed-off-by: Peng Fan
---
xen/arch/arm/mm.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/xen/arch/arm/mm.c b/xen/arch/arm
The end should be GICD_ISACTIVERN not GICD_ISACTIVER,
and also print a warning for the unhandled read.
Signed-off-by: Peng Fan
---
V2:
Add a warning message
xen/arch/arm/vgic-v3.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/xen/arch/arm/vgic-v3.c b/xen/arch/arm
Hi All,
I am trying vsnd from xen-troops with xen 4.13 and Linux 5.4, but domu reports:
aplay compl.mp3
ALSA lib
../../../alsa-lib-1.1.9/src/pcm/pcm_direct.c:1156:(snd1_pcm_direct_initialize_slave)
slave plugin does not support mmap interleaved or mmap noninterleaved access
ALSA lib ../../../als
> Cc: sstabell...@kernel.org; jul...@xen.org; xen-de...@lists.xen.org
> Subject: Re: [Xen-devel] vsnd issue
>
> On 11/25/19 12:40 PM, Artem Mygaiev wrote:
> > Hello Peng Fan
> >
> > Please contact Oleksandr Andrushchenko (added to this thread) on this
> > issu
> Subject: Re: [Xen-devel] [PATCH V2] arch: arm: vgic-v3: fix GICD_ISACTIVER
> range
>
> On 27.11.19 01:01, Julien Grall wrote:
> > Hi,
> >
> > On 26/11/2019 23:17, Stefano Stabellini wrote:
> >> On Tue, 26 Nov 2019, Julien Grall wrote:
> >>> Hi,
> >>>
> >>> On 26/11/2019 20:43, Stefano Stabellini
> Subject: Re: [Xen-devel] [PATCH V2] arch: arm: vgic-v3: fix GICD_ISACTIVER
> range
>
> On 27.11.19 10:31, Peng Fan wrote:
> >> Subject: Re: [Xen-devel] [PATCH V2] arch: arm: vgic-v3: fix
> >> GICD_ISACTIVER range
> >>
> >> On 27.11.19 01:01, Ju
> Subject: Re: [Xen-devel] [PATCH V2] arch: arm: vgic-v3: fix GICD_ISACTIVER
> range
>
> Hi Stefano,
>
> On 28/11/2019 01:12, Stefano Stabellini wrote:
> > On Wed, 27 Nov 2019, Jürgen Groß wrote:
> >> On 27.11.19 10:31, Peng Fan wrote:
> >>>> Sub
The end should be GICD_ISACTIVERN not GICD_ISACTIVER.
Signed-off-by: Peng Fan
---
xen/arch/arm/vgic-v3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/arm/vgic-v3.c b/xen/arch/arm/vgic-v3.c
index 422b94f902..e802f2055a 100644
--- a/xen/arch/arm/vgic-v3.c
+++ b/xen
Hi Julien,
Inline marked with [Peng Fan]
From: Julien Grall
Sent: 2019年11月9日 6:44
To: Stefano Stabellini ; Andre Przywara
Cc: Peng Fan ; Jürgen Groß ;
julien.gr...@arm.com; xen-de...@lists.xen.org
Subject: Re: [Xen-devel] [PATCH] arch: arm: vgic-v3: fix GICD_ISACTIVER range
Hi,
Sorry for
> Do you have a call stack trace for this?
(XEN) d0v1: vGICD: unhandled read r1 offset 0x000324
(XEN) traps.c:1994:d0v1 HSR=0x93810006 pc=0x8000104f2bb4
gva=0x800010010324 gpa=0x0051a00324
[1.780564] Unhandled fault at 0x800010010324
[1.785771] Mem abort info:
[1.7888
Hi Oleksandr,
Just have a question, is this drm/xen-front stuff orthogonal to xen shared
coprocessor framework for gpu, or are they exclusive?
Thanks,
Peng.
> Subject: [Xen-devel] [PATCH v6 0/1] drm/xen-front: Add support for Xen PV
> display frontend
>
> From: Oleksandr Andrushchenko
>
> Hell
Hi Edgar,
> -Original Message-
> From: Edgar E. Iglesias [mailto:edgar.igles...@xilinx.com]
> Sent: 2018年3月26日 19:43
> To: Peng Fan
> Cc: Mirela Simonovic ; xen-de...@lists.xen.org;
> sstabell...@kernel.org; julien.gr...@linaro.org
> Subject: Re: [Xen-devel] [RFC v2
Hi Stefano,
On Fri, Mar 02, 2018 at 11:05:54AM -0800, Stefano Stabellini wrote:
>Hi all,
>
>This series changes the initialization of two virtual registers to make
>sure they match the value of the underlying physical cpu.
>
>It also disables cpus different from the boot cpu, unless a newly
>introd
> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf Of
> Julien Grall
> Sent: 2018年3月8日 19:04
> To: Peng Fan ; Stefano Stabellini
>
> Cc: xen-de...@lists.xen.org
> Subject: Re: [Xen-devel] [PATCH v4 0/7] unsafe big.L
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 2018年3月8日 20:30
> To: Peng Fan ; Peng Fan ;
> Stefano Stabellini
> Cc: xen-de...@lists.xen.org
> Subject: Re: [Xen-devel] [PATCH v4 0/7] unsafe big.LITTLE support
>
> Hi,
>
On Thu, Mar 08, 2018 at 03:13:50PM +, Julien Grall wrote:
>Hi,
>
>On 08/03/18 12:43, Peng Fan wrote:
>>>>>>I am not sure whether this issue cause DomU big/Little not work.
>>>>>
>>>>>Well, I would recommend to speak with NXP whether thi
Hi Julien,
On Fri, Mar 09, 2018 at 10:22:09AM +, Julien Grall wrote:
>Hi Peng,
>
>On 09/03/18 09:05, Peng Fan wrote:
>>On Thu, Mar 08, 2018 at 03:13:50PM +, Julien Grall wrote:
>>>On 08/03/18 12:43, Peng Fan wrote:
>>>There are a major difference be
On Fri, Mar 09, 2018 at 02:40:25PM +, Julien Grall wrote:
>Hi,
>
>On 09/03/18 13:30, Peng Fan wrote:
>>Hi Julien,
>>On Fri, Mar 09, 2018 at 10:22:09AM +, Julien Grall wrote:
>>>Hi Peng,
>>>
>>>On 09/03/18 09:05, Peng Fan wrote:
>>&g
Hi Stefano,
On Fri, Mar 09, 2018 at 05:09:20PM -0800, Stefano Stabellini wrote:
>On Fri, 9 Mar 2018, Julien Grall wrote:
>> Furthermore, the workaround is not in Linux upstream and I doubt this will be
>> accepted as it is. So I am not convinced that we should modify Xen interface
>> for that.
>>
Hi Mirela,
Good to know that you are working suspend/resume support. Currently we are also
trying
to support this on i.MX8, just wonder do you have any open source available to
support suspend to ram?
> +
> +Suspend to RAM (in the following text 'suspend') for ARM in Xen should
> +be coordinated
Hi,
I am bringing up android on XEN on ARM, but android needs some features in
bootloader, such as A/B slot, dm verify and etc. With directly booting android
kernel, I could successfully boot up android directly passthrough emmc
controller to android OS. I am thinking to develop U-Boot on XEN t
Hi Stefano,
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 2018年5月30日 6:49
> To: Peng Fan
> Cc: Julien Grall ; sstabell...@kernel.org;
> andrii_ani...@epam.com; xen-devel@lists.xenproject.org;
> anthony.per...@citrix.com
>
Hi Julien, Stefano,
Do you have any suggestions on how to share one interrupt between Doms?
The issue is that a gpio controller has 32 in/out port, however it only has one
binded interrupt. The interrupt handler needs to check the status bits to check
which port has interrupt coming.
In my case,
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 2018年10月3日 0:03
> To: Peng Fan ; Stefano Stabellini
> Cc: xen-devel@lists.xenproject.org; Andre Przywara
>
> Subject: Re: Question, How to share interrupt between Doms
>
> On
Hi Julien
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 2018年10月5日 1:27
> To: Peng Fan ; Stefano Stabellini
> Cc: xen-devel@lists.xenproject.org; Andre Przywara
>
> Subject: Re: Question, How to share interrupt between Doms
>
Hi All,
Just have a question, does XEN ARM support RTC in domu? To support Android in
DomU, RTC is needed for alarm, but I did not find information about RTC on xen
for domu. So this need a new RTC paravirtualization driver? Any suggestions?
Thanks,
Peng.
__
Hi Julien,
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 2018年11月1日 2:52
> To: Peng Fan ; xen-devel@lists.xenproject.org; Stefano
> Stabellini
> Subject: Re: Does XEN ARM support RTC in domu?
>
>
>
> On 10/31/18 1:57
Hi Julien,
> >>
> >>>
> >>> Just have a question, does XEN ARM support RTC in domu? To support
> >>> Android
> >> in DomU, RTC is needed for alarm, but I did not find information
> >> about RTC on xen for domu. So this need a new RTC paravirtualization
> >> driver?
> Any suggestions?
> >>
> >> By
Hi Julien,
> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf Of
> Peng Fan
> Sent: 2018年11月5日 10:11
> To: Julien Grall ; xen-devel@lists.xenproject.org;
> Stefano Stabellini
> Subject: Re: [Xen-devel] Does XEN AR
still not public now.
Regards,
Peng.
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@arm.com]
> Sent: 2018年11月7日 3:06
> To: Stefano Stabellini ; Ravi Pichholiya
>
> Cc: xen-de...@lists.xen.org; Peng Fan
> Subject: Re: Porting XEN hypervisor on iMX8QM
>
Hi,
I am trying to enable pv console in domu uboot without interrupt, but not work
well,
When using xl console to attach domu, there are only a few chars output.
I add some debug info in write_console, and see out_cons are not increased after
notify_remote_by_evtchn. The write_console is taken f
Resolved, did not setup xen magic pages in proper mmu settings.
Regards,
Peng.
> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf
> Of Peng Fan
> Sent: 2018年11月14日 18:22
> To: xen-devel@lists.xenproject.org
> Cc: Juli
From: Peng Fan
When booting xen on i.MX8QM, met:
"
[3.602128] Unable to handle kernel paging request at virtual address
00272d40
[3.610804] Mem abort info:
[3.613905] ESR = 0x9604
[3.617332] EC = 0x25: DABT (current EL), IL = 32 bits
[3.623211] SET = 0
age_boundary(phys, size) are true, it will create
> > contiguous region. So when free, we need to free contiguous region use
> > upper check condition.
> >
> > Signed-off-by: Peng Fan
> > ---
> > drivers/xen/swiotlb-xen.c | 4 ++--
> > 1 file changed, 2 ins
> Subject: Re: [PATCH] xen/swiotlb: correct the check for
> xen_destroy_contiguous_region
>
> On 28.04.20 09:33, peng@nxp.com wrote:
> > From: Peng Fan
> >
> > When booting xen on i.MX8QM, met:
> > "
> > [3.602128] Unable to
> Subject: Re: Troubles running Xen on Raspberry Pi 4 with 5.6.1 DomU
>
> On 06.05.20 00:34, Stefano Stabellini wrote:
> > + Boris, Jürgen
> >
> > See the crash Roman is seeing booting dom0 on the Raspberry Pi. It is
> > related to the recent xen dma_ops changes. Possibly the same thing
> > report
Grall ;
> Nataliya Korovkina
> Subject: UEFI support in ARM DomUs
We have made U-Boot run inside XEN DomU, but just only PV console part,
not implement other frontend drivers currently. Would this help for your
case if enable EFI in U-Boot?
Regards,
Peng.
>
> Hi!
>
> with a lot of help from S
Hi Stefano,
> -Original Message-
> From: Stefano Stabellini [mailto:sstabell...@kernel.org]
> Sent: 2020年6月4日 23:32
> To: Oleksandr Andrushchenko
> Cc: Peng Fan ; Roman Shaposhnik
> ; Xen-devel ; Stefano
> Stabellini ; Julien Grall ; Nataliya
> Korovkina
> S
Hi All,
While enabling trusty os with xen, I took same approach as OP-TEE,
with OP-TEE running in secure world. But I am also thinking this might
introduce potential issue is that secure world OS communicate with DomU.
If there are some misbehavior in secure world OS, it might let XEN
hypervisor
Hi,
> Subject: Re: [Tee-dev] TEE with XEN
>
> Hi Peng,
>
> On Mon, 15 Jun 2020 at 05:07, Peng Fan wrote:
> >
> > Hi All,
> >
> > While enabling trusty os with xen, I took same approach as OP-TEE,
> > with OP-TEE running in secure world. But I am als
Hi Bertrand,
> Subject: Re: [Tee-dev] TEE with XEN
>
> Hi,
>
> > On 18 Jun 2020, at 19:05, Julien Grall wrote:
> >
> > +Bertrand and Stefano
> >
> > On 16/06/2020 02:24, Volodymyr Babchuk wrote:
> >> Hi Peng,
> >> On Mo
> Subject: Re: [Tee-dev] TEE with XEN
>
>
>
> > On 19 Jun 2020, at 09:52, Peng Fan wrote:
> >
> > Hi Bertrand,
> >
> >> Subject: Re: [Tee-dev] TEE with XEN
> >>
> >> Hi,
> >>
> >>> On 18 Jun 2020, at 19:05, Ju
> Subject: Re: [Tee-dev] TEE with XEN
>
> Hi Peng,
>
> On Fri, 19 Jun 2020 at 12:06, Peng Fan wrote:
> >
> > > Subject: Re: [Tee-dev] TEE with XEN
> > >
> > >
> > >
> > > > On 19 Jun 2020, at 09:52, Peng Fan wrote:
> >
> Subject: Re: UEFI support in ARM DomUs
>
>
> On 6/19/20 3:59 PM, Julien Grall wrote:
> > Hi,
> >
> > On 19/06/2020 13:51, Oleksandr Andrushchenko wrote:
> >> On 6/19/20 3:47 PM, Julien Grall wrote:
> >>> They will not be available from the fdt, but you can retrieve them with an
> hypervisor cal
> Subject: Re: UEFI support in ARM DomUs
>
>
> On 6/23/20 8:31 AM, Oleksandr Andrushchenko wrote:
> >
> > On 6/23/20 4:20 AM, Stefano Stabellini wrote:
> >> On Mon, 22 Jun 2020, Julien Grall wrote:
> >> For the first part (__XEN_INTERFACE_VERSION__) I think we can
> >> provide it via
> >>
> Subject: Re: UEFI support in ARM DomUs
>
>
> On 6/24/20 10:07 AM, Peng Fan wrote:
> >> Subject: Re: UEFI support in ARM DomUs
> >>
> >>
> >> On 6/23/20 8:31 AM, Oleksandr Andrushchenko wrote:
> >>> On 6/23/20 4:20 AM, Stefano Stab
Export xen_swiotlb for all platforms using xen swiotlb
Use xen_swiotlb to determine when vring should use dma APIs to map the
ring: when xen_swiotlb is enabled the dma API is required. When it is
disabled, it is not required.
Signed-off-by: Peng Fan
---
V2:
This is a modified version from
4, 2020 at 10:59:47AM -0700, Stefano Stabellini wrote:
> > > > > On Wed, 24 Jun 2020, Michael S. Tsirkin wrote:
> > > > > > On Wed, Jun 24, 2020 at 05:17:32PM +0800, Peng Fan wrote:
> > > > > > > Export xen_swiotlb for all platforms using xen swiot
> On Wed, 24 Jun 2020, Michael S. Tsirkin wrote:
> > > > > On Wed, Jun 24, 2020 at 10:59:47AM -0700, Stefano Stabellini wrote:
> > > > > > On Wed, 24 Jun 2020, Michael S. Tsirkin wrote:
> > > > > > > On Wed, Jun 24, 2020 at 05:17:32PM +08
> Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
>
> On Mon, Jun 29, 2020 at 03:05:19AM +0000, Peng Fan wrote:
> > > Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
> > >
> > > On Thu, Jun 25, 2020 at 10:31:27AM -0700, Stefano Stabellini wrote:
&g
> Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
>
> On Mon, Jun 29, 2020 at 06:25:41AM +0000, Peng Fan wrote:
> > > > > > Anyway, re-reading the last messages of the original thread
> > > > > > [1], it looks like Peng had a clear idea
> Subject: RE: [PATCH] xen: introduce xen_vring_use_dma
>
> On Mon, 29 Jun 2020, Peng Fan wrote:
> > > > If that is the case, how is it possible that virtio breaks on ARM
> > > > using the default dma_ops? The breakage is not Xen related (except
> > >
> Subject: Re: [PATCH] xen: introduce xen_vring_use_dma
>
> Sorry for the late reply -- a couple of conferences kept me busy.
>
>
> On Wed, 1 Jul 2020, Michael S. Tsirkin wrote:
> > On Wed, Jul 01, 2020 at 10:34:53AM -0700, Stefano Stabellini wrote:
> > > Would you be in favor of a more flexible
arm64 shares some code under arch/arm/xen, including mm.c.
However ZONE_DMA is removed by commit
ad67f5a6545("arm64: replace ZONE_DMA with ZONE_DMA32").
So to ARM64, need use __GFP_DMA32.
Signed-off-by: Peng Fan
---
arch/arm/xen/mm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletio
ARM64, need use __GFP_DMA32.
>
> Signed-off-by: Peng Fan
> ---
> arch/arm/xen/mm.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/xen/mm.c b/arch/arm/xen/mm.c index
> e1d44b903dfc..a95e76d18bf9 100644
> --- a/arch/arm/xen/mm.c
>
Hi Kelly,
Wonder whether there will be recording or notes for this and public later?
Thanks,
Peng.
From: Xen-users On Behalf Of Kelly Choi
Sent: Wednesday, September 25, 2024 10:59 PM
To: xen-devel ; xen-us...@lists.xenproject.org
Subject: [POLL] Interest in next Xen Project meetup (Cambridge)
Hi Julien,
> Subject: Re: [PATCH 1/3] xen/arm: Add i.MX lpuart driver
>
> Hi Peng,
>
> On 28/02/2022 01:07, Peng Fan (OSS) wrote:
> > From: Peng Fan
> >
> > Signed-off-by: Peng Fan
> > ---
> > xen/drivers/char/Kconfig | 8 +
> >
> Subject: Re: [PATCH 3/3] xen/arm: Add i.MX8QM platform support
>
> Hi Peng,
>
> On 28/02/2022 01:07, Peng Fan (OSS) wrote:
> > From: Peng Fan
> >
> > Signed-off-by: Peng Fan
> > ---
> > xen/arch/arm/Kconfig.debug | 3 +++
> > xen/ar
> Subject: Re: [PATCH 2/3] xen/arm: Add i.MX lpuart early printk support
>
> Hi Peng,
>
> On 28/02/2022 01:07, Peng Fan (OSS) wrote:
> > From: Peng Fan
> >
> > Signed-off-by: Peng Fan
> > ---
> > xen/arch/arm/Kconfig.debug | 18
> Subject: Re: [PATCH V2 1/2] xen/arm: Add i.MX lpuart driver
>
> Hi Peng,
>
> On 02.04.2022 07:42, Peng Fan (OSS) wrote:
> > From: Peng Fan
> >
> > The i.MX LPUART Documentation:
> >
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2
Hi Michal,
> -Original Message-
> From: Michal Orzel [mailto:michal.or...@arm.com]
> Sent: 2022年4月8日 18:23
> To: Peng Fan (OSS) ; sstabell...@kernel.org;
> jul...@xen.org; volodymyr_babc...@epam.com;
> bertrand.marq...@arm.com
> Cc: andrew.coop...@citrix.com; geo
> Subject: Re: [PATCH V5 1/2] xen/arm: Add i.MX lpuart driver
>
> On Thu, 14 Apr 2022, Peng Fan (OSS) wrote:
> > From: Peng Fan
> >
> > The i.MX LPUART Documentation:
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> >
> Subject: Re: [PATCH 0/3] xen/arm: add i.MX lpuart and i.MX8QM initial
> support
>
> On 28.02.2022 02:07, Peng Fan (OSS) wrote:
> > From: Peng Fan
> >
> > Add i.MX lpuart driver and i.MX8QM platform support.
> > - lpuart is the uart IP used in i.MX8QM/QXP/93
Hi Julien,
> Subject: Re: [PATCH 1/3] xen/arm: Add i.MX lpuart driver
>
> Hi Peng,
>
> On 28/02/2022 01:07, Peng Fan (OSS) wrote:
> > From: Peng Fan
>
> Can you give me a link to the specification and/or a similar driver in Linux?
https://www.nxp.com/webapp
Hi All,
I am trying to enable vhost user input with xen hypervisor on i.MX95, using qemu
vhost-user-input. But meet " Invalid vring_addr message ". My xen domu cfg:
'-chardev', 'socket,path=/tmp/input.sock,id=mouse0',
'-device', 'vhost-user-input-pci,chardev=mouse0',
Anyone knows what missing?
> Subject: Re: Question: xen + vhost user
>
> +Edgar
>
> I don't think we are using vhost-user so I am unable to help, but adding
> Edgar just in case
Thanks, just an update, it works after some code changes to Qemu.
Thanks,
Peng.
>
> On Sun, 30 Jun 202
c2b
> 4c6fa92cd99c5c301635%7C0%7C0%7C637895208732114203%7CUnknown%
> 7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL
> CJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=no%2BV2ubjGmrsm96NP
> ybeeug4a3BXx3oX7xmylzZCU8E%3D&reserved=0.
>
> After some investigation I found that this i
> Subject: Re: [Xen-devel] SMMU permission fault on Dom0 when init
> vpu_decoder
>
> On Wed, Jun 01, 2022 at 07:59:23AM +0000, Peng Fan wrote:
> > > Subject: [Xen-devel] SMMU permission fault on Dom0 when init
> > > vpu_decoder
> > >
> > > Hello,
&g
sb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL
> CJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KcbEjN80VJS5yq4KMp2g
> NjQuVtx95jKHH5T32ZCj3Do%3D&reserved=0.
> >
> > After some investigation I found that this issue was fixed by Peng Fan
> > in
> &
> Subject: Re: [PATCH 1/2] xen/arm: Add imx8q{m,x} platform glue
>
> On Wed, 20 Mar 2024, Julien Grall wrote:
> > Hi John,
> >
> > On 20/03/2024 16:24, John Ernberg wrote:
> > > Hi Bertrand,
> > >
> > > On 3/13/24 11:07, Bertrand Marquis wrote:
> > > > Hi,
> > > >
> > > > > On 8 Mar 2024, at 15:04
Hi Oleksandr,
> Subject: [PATCH 2/2] xen/arm: Add i.MX UART driver
>
> From: Oleksandr Tyshchenko
>
> The i.MX UART Documentation:
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> nxp.com%2Fwebapp%2FDownload%3FcolCode%3DIMX8MMRM&data=05%7
> C02%7Cpeng.fan%40nxp.com%7C6
t_init(struct
> dt_device_node *dev,
>
> static const struct dt_device_match imx_lpuart_dt_compat[] __initconst = {
> -DT_MATCH_COMPATIBLE("fsl,imx8qm-lpuart"),
> +DT_MATCH_COMPATIBLE("fsl,imx8qxp-lpuart"),
> { /* sentinel */ },
Reviewed-by: Peng Fan
> };
>
> --
> 2.44.0
%2Farm%2Fplatforms%2Fimx8qm.c&data=05%7
> C02%7Cpeng.fan%40nxp.com%7C5602a2d54f074c7dcd9608dc57e69286%7
> C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C6384818950076004
> 32%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMz
> IiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&
g
> +F: xen/arch/arm/platforms/imx8qm.c
> +F: xen/drivers/char/imx-lpuart.c
> +
> INTEL(R) TRUSTED EXECUTION TECHNOLOGY (TXT)
> R: Lukasz Hawrylko
> R: Daniel P. Smith
> --
Acked-by: Peng Fan
Hi Julien, John,
> Subject: Re: [PATCH v4 1/3] xen/arm: Add imx8q{m,x} platform glue
>
> Hi John,
>
> On 15/04/2024 12:17, John Ernberg wrote:
> > Hi Julien,
> >
> > On 4/15/24 1:03 PM, Julien Grall wrote:
> >>
> >>
> >> On 15/04/2024 11:50, Andrew Cooper wrote:
> >>> On 15/04/2024 11:25 am, Julie
1 - 100 of 134 matches
Mail list logo
