mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gupta, Pankaj" <pankaj.gupta@amd.com>
To: Kevin Loughlin <kevinloughlin@google.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	nvdimm@lists.linux.dev, linux-cxl@vger.kernel.org,
	linux-kernel@vger.kernel.org, changyuanl@google.com,
	pgonda@google.com, sidtelang@google.com, tytso@mit.edu,
	pasha.tatashin@soleen.com, thomas.lendacky@amd.com
Subject: Re: [PATCH] device-dax: map dax memory as decrypted in CoCo guests
Date: Tue, 10 Sep 2024 15:00:09 +0200	[thread overview]
Message-ID: <78cbbaca-5413-c006-6609-ee23e2c757f0@amd.com> (raw)
In-Reply-To: <CAGdbjmLVFZJq7OJv2OwM3knmwfb-j8nZP7G_ownFA3kd3fYbVA@mail.gmail.com>

On 8/26/2024 11:35 PM, Kevin Loughlin wrote:
>> How can I test this? Can I test it with virtio-pmem device?
> 
> Correct. Assuming the CoCo guest accesses some virtio-pmem device in
> devdax mode, mmapping() this virtio-pmem device's memory region
> results in the guest and host reading the same (plaintext) values from
> the region.

I tried to test the daxdev with virtio-pmem but getting the below error 
(just tried without this patch)

root@ubuntu:/home/amd# ndctl list -N
{
   "dev":"namespace0.0",
   "mode":"devdax",
   "map":"dev",
   "size":1054867456,
   "uuid":"c8b15ce6-0c8f-4a1a-ada6-b19a90bdf1bb",
   "numa_node":0
}

root@ubuntu:cat /dev/zero | daxio --output=/dev/namespace0.0
daxio: neither input or output is device dax

Could you please share the instructions (to test with virtio-pmem or 
Qemu). If not, still okay.

Thanks,
Pankaj
Best regards,
Pankaj

  reply	other threads:[~2024-09-10 13:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-14 20:53 Kevin Loughlin
2024-08-23 12:09 ` Gupta, Pankaj
2024-08-26 21:35   ` Kevin Loughlin
2024-09-10 13:00     ` Gupta, Pankaj [this message]
2024-09-10 13:07       ` Gupta, Pankaj

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=78cbbaca-5413-c006-6609-ee23e2c757f0@amd.com \
    --to=pankaj.gupta@amd.com \
    --cc=changyuanl@google.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=kevinloughlin@google.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=pasha.tatashin@soleen.com \
    --cc=pgonda@google.com \
    --cc=sidtelang@google.com \
    --cc=thomas.lendacky@amd.com \
    --cc=tytso@mit.edu \
    --cc=vishal.l.verma@intel.com \
    /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
all inboxes | Powered by JetHome®