From: Marc Zyngier <maz@kernel.org>
To: 谢明 <xieming@kylinos.cn>
Cc: linux-kernel@vger.kernel.org, christoffer.dall@arm.com,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu
Subject: Re: 回复: Re: [PATCH] kvm: fix gpu passthrough into vm on arm64
Date: Fri, 25 Mar 2022 13:06:15 +0000 [thread overview]
Message-ID: <87ils25ghk.wl-maz@kernel.org> (raw)
In-Reply-To: <1zpfpvw7azf-1zpgztpmct8@nsmail6.0>
On Fri, 25 Mar 2022 01:06:17 +0000,
谢明 <xieming@kylinos.cn> wrote:
>
> thanks for your reply !
> you are right, 'If the device supports NORMAL_NC, this should
> be known by the host kernel and exposed to KVM'， accordding the kvm
> combining rules on arm64， stage1 is setting to NORMAL_NC， so can
> we add a conditional judement when ioremapping on stage2, if the
> device suppurt NORMAL_NC we setting the memory attribute to
> PAGE_S2_NC ?
The question remains: how do you convey that capability to the host?
There is nothing currently telling KVM what memory type to use.
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: 谢明 <xieming@kylinos.cn>
Cc: <christoffer.dall@arm.com>, <kvmarm@lists.cs.columbia.edu>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: 回复: Re: [PATCH] kvm: fix gpu passthrough into vm on arm64
Date: Fri, 25 Mar 2022 13:06:15 +0000 [thread overview]
Message-ID: <87ils25ghk.wl-maz@kernel.org> (raw)
In-Reply-To: <1zpfpvw7azf-1zpgztpmct8@nsmail6.0>
On Fri, 25 Mar 2022 01:06:17 +0000,
谢明 <xieming@kylinos.cn> wrote:
>
> thanks for your reply !
> you are right, 'If the device supports NORMAL_NC, this should
> be known by the host kernel and exposed to KVM'， accordding the kvm
> combining rules on arm64， stage1 is setting to NORMAL_NC， so can
> we add a conditional judement when ioremapping on stage2, if the
> device suppurt NORMAL_NC we setting the memory attribute to
> PAGE_S2_NC ?
The question remains: how do you convey that capability to the host?
There is nothing currently telling KVM what memory type to use.
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
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: 谢明 <xieming@kylinos.cn>
Cc: <christoffer.dall@arm.com>, <kvmarm@lists.cs.columbia.edu>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: 回复: Re: [PATCH] kvm: fix gpu passthrough into vm on arm64
Date: Fri, 25 Mar 2022 13:06:15 +0000 [thread overview]
Message-ID: <87ils25ghk.wl-maz@kernel.org> (raw)
In-Reply-To: <1zpfpvw7azf-1zpgztpmct8@nsmail6.0>
On Fri, 25 Mar 2022 01:06:17 +0000,
谢明 <xieming@kylinos.cn> wrote:
>
> thanks for your reply !
> you are right, 'If the device supports NORMAL_NC, this should
> be known by the host kernel and exposed to KVM'， accordding the kvm
> combining rules on arm64， stage1 is setting to NORMAL_NC， so can
> we add a conditional judement when ioremapping on stage2, if the
> device suppurt NORMAL_NC we setting the memory attribute to
> PAGE_S2_NC ?
The question remains: how do you convey that capability to the host?
There is nothing currently telling KVM what memory type to use.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2022-03-25 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 1:06 回复: Re: [PATCH] kvm: fix gpu passthrough into vm on arm64 谢明
2022-03-25 13:06 ` Marc Zyngier [this message]
2022-03-25 13:06 ` Marc Zyngier
2022-03-25 13:06 ` 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=87ils25ghk.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=christoffer.dall@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xieming@kylinos.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.