From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Lira, Victor M" <victorm.lira@amd.com>
Cc: "Jan Beulich" <jbeulich@suse.com>,
"Jason Andryuk" <jason.andryuk@amd.com>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
Xenia.Ragiadakou@amd.com, Alejandro.GarciaVallejo@amd.com
Subject: Re: [RFC] xen/x86: allow overlaps with non-RAM regions
Date: Thu, 15 May 2025 12:19:19 +0200 [thread overview]
Message-ID: <aCW_p_ucNFaFFLeo@macbook.lan> (raw)
In-Reply-To: <02b6f10a-119e-499c-a51f-8deac6fa6a93@amd.com>
On Mon, May 12, 2025 at 10:55:18AM -0700, Lira, Victor M wrote:
> On 5/12/2025 9:16 AM, Roger Pau Monné wrote:
> > Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
> >
> >
> > On Fri, Apr 25, 2025 at 09:47:57AM -0700, Lira, Victor M wrote:
> > > I can confirm with the patch the NVME drive can be accessed despite the "not
> > > mapping BAR" warning from Xen.
> > > Output log attached.
> > Thanks a lot for the test, and sorry for the delay in getting back. I
> > was busy with other stuff and needed some time to figure out the best
> > way to deal with this. Can you give a try to the patch below? I hope
> > it will still fix the issue.
> No worries, I applied this patch to the latest staging c45e57f59d69, and
> the result is also successful NVME drive access.
> Output log attached and I see no "failed to sanitize" warnings.
Thanks for the testing.
I've formally submitted this as:
https://lore.kernel.org/xen-devel/20250515084123.43289-1-roger.pau@citrix.com/
Functionality wise I think it should be the same as the last patch you
tried. Could you give it a spin and maybe provide a Tested-by if
suitable?
Thanks, Roger.
next prev parent reply other threads:[~2025-05-15 10:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 1:01 [RFC] xen/x86: allow overlaps with non-RAM regions Stefano Stabellini
2025-04-04 8:07 ` Jan Beulich
2025-04-10 20:55 ` Jason Andryuk
2025-04-11 7:56 ` Jan Beulich
2025-04-04 10:28 ` Roger Pau Monné
2025-04-10 20:55 ` Jason Andryuk
2025-04-11 7:31 ` Roger Pau Monné
2025-04-11 8:07 ` Jan Beulich
2025-04-11 13:45 ` Jason Andryuk
2025-04-14 8:25 ` Roger Pau Monné
2025-04-23 23:51 ` Lira, Victor M
2025-04-24 7:59 ` Roger Pau Monné
2025-04-24 10:15 ` Marek Marczykowski-Górecki
2025-04-24 10:48 ` Roger Pau Monné
2025-04-24 21:19 ` Jason Andryuk
2025-04-24 21:38 ` Lira, Victor M
2025-04-25 9:02 ` Roger Pau Monné
2025-04-25 9:19 ` Jan Beulich
2025-04-25 11:09 ` Roger Pau Monné
2025-04-25 16:47 ` Lira, Victor M
2025-05-12 16:16 ` Roger Pau Monné
2025-05-12 17:55 ` Lira, Victor M
2025-05-15 10:19 ` Roger Pau Monné [this message]
2025-05-15 16:24 ` Lira, Victor M
2025-04-11 8:15 ` Jan Beulich
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=aCW_p_ucNFaFFLeo@macbook.lan \
--to=roger.pau@citrix.com \
--cc=Alejandro.GarciaVallejo@amd.com \
--cc=Xenia.Ragiadakou@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=jason.andryuk@amd.com \
--cc=jbeulich@suse.com \
--cc=marmarek@invisiblethingslab.com \
--cc=sstabellini@kernel.org \
--cc=victorm.lira@amd.com \
--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 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.