From: Wei Liu <wei.liu@kernel.org>
To: "Yu, Lang" <Lang.Yu@amd.com>
Cc: Wei Liu <wei.liu@kernel.org>,
Iouri Tarassov <iourit@linux.microsoft.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.org>
Subject: Re: [PATCH] drivers: hv: dxgkrnl: Allow user to specify CPU VA for device allocation
Date: Wed, 17 Jan 2024 03:02:34 +0000 [thread overview]
Message-ID: <ZadDSqEkTxVIxBZj@liuwe-devbox-debian-v2> (raw)
In-Reply-To: <MW6PR12MB889841CC7947959A0A3AEC0FFB722@MW6PR12MB8898.namprd12.prod.outlook.com>
On Wed, Jan 17, 2024 at 02:59:55AM +0000, Yu, Lang wrote:
> [Public]
>
> >-----Original Message-----
> >From: Wei Liu <wei.liu@kernel.org>
> >Sent: Wednesday, January 17, 2024 10:53 AM
> >To: Yu, Lang <Lang.Yu@amd.com>
> >Cc: Iouri Tarassov <iourit@linux.microsoft.com>; linux-hyperv@vger.kernel.org;
> >Wei Liu <wei.liu@kernel.org>
> >Subject: Re: [PATCH] drivers: hv: dxgkrnl: Allow user to specify CPU VA for device
> >allocation
> >
> >On Tue, Jan 16, 2024 at 01:58:53PM +0000, Yu, Lang wrote:
> >> [Public]
> >>
> >> ping
> >>
> >> >-----Original Message-----
> >> >From: Yu, Lang <Lang.Yu@amd.com>
> >> >Sent: Wednesday, December 27, 2023 11:50 AM
> >> >To: Iouri Tarassov <iourit@linux.microsoft.com>
> >> >Cc: linux-hyperv@vger.kernel.org; Yu, Lang <Lang.Yu@amd.com>
> >> >Subject: [PATCH] drivers: hv: dxgkrnl: Allow user to specify CPU VA
> >> >for device allocation
> >> >
> >> >The movtivation is we want to unify CPU VA and GPU VA.
> >> >
> >> >Signed-off-by: Lang Yu <Lang.Yu@amd.com>
> >
> >Hi Lang,
> >
> >The driver is not merged upstream. I won't take any further action here because
> >there is nothing I can do. Perhaps you can work directly with Iouri to merge the
> >change to the driver he maintains.
>
> Thanks. Got it.
> https://github.com/microsoft/WSL2-Linux-Kernel?tab=readme-ov-file#feature-requests tells me submitting the change upstream.
That's true in general,but in this case because the driver itself is not
upstreamed yet so it cannot be applied.
Don't let this discourage you. If you author changes to code that is
already upstreamed, do submit them to the respective mailing lists.
Thanks,
Wei.
>
> Regards,
> Lang
>
> >Thanks,
> >Wei.
prev parent reply other threads:[~2024-01-17 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 3:49 [PATCH] drivers: hv: dxgkrnl: Allow user to specify CPU VA for device allocation Lang Yu
2024-01-16 13:58 ` Yu, Lang
2024-01-17 2:53 ` Wei Liu
2024-01-17 2:59 ` Yu, Lang
2024-01-17 3:02 ` Wei Liu [this message]
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=ZadDSqEkTxVIxBZj@liuwe-devbox-debian-v2 \
--to=wei.liu@kernel.org \
--cc=Lang.Yu@amd.com \
--cc=iourit@linux.microsoft.com \
--cc=linux-hyperv@vger.kernel.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