From: Klaus Jensen <its@irrelevant.dk>
To: Andrzej Jakowski <andrzej.jakowski@linux.intel.com>
Cc: kbusch@kernel.org, kwolf@redhat.com, qemu-devel@nongnu.org,
qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [PATCH v4 2/2] nvme: allow cmb and pmr to be enabled on same device
Date: Wed, 15 Jul 2020 10:21:06 +0200 [thread overview]
Message-ID: <20200715082106.GA530932@apples.localdomain> (raw)
In-Reply-To: <20200715080658.GA506302@apples.localdomain>
On Jul 15 10:06, Klaus Jensen wrote:
>
> Can you reproduce the issues with that patch? I can't on a stock Arch
> Linux 5.7.5-arch1-1 kernel.
>
Was afraid I said this a bit too early since the stock kernel does not
enable the iommu by default. Tested with another kernel and yes, I still
cannot reproduce the vtd errors or any complaints from the kernel (w/
or w/o iommu).
next prev parent reply other threads:[~2020-07-15 8:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 21:48 [PATCH v4] nvme: allow cmb and pmr emulation on same device Andrzej Jakowski
2020-07-01 21:48 ` [PATCH v4 1/2] nvme: indicate CMB support through controller capabilities register Andrzej Jakowski
2020-07-07 16:27 ` Maxim Levitsky
2020-07-07 19:15 ` Klaus Jensen
2020-07-30 11:26 ` Maxim Levitsky
2020-07-01 21:48 ` [PATCH v4 2/2] nvme: allow cmb and pmr to be enabled on same device Andrzej Jakowski
2020-07-02 10:13 ` Klaus Jensen
2020-07-02 10:31 ` Klaus Jensen
2020-07-02 15:07 ` Andrzej Jakowski
2020-07-02 17:51 ` Klaus Jensen
2020-07-02 23:33 ` Andrzej Jakowski
2020-07-06 7:15 ` Klaus Jensen
2020-07-08 4:44 ` Andrzej Jakowski
2020-07-15 8:06 ` Klaus Jensen
2020-07-15 8:21 ` Klaus Jensen [this message]
2020-07-21 21:54 ` Andrzej Jakowski
2020-07-22 7:43 ` Klaus Jensen
2020-07-22 17:00 ` Andrzej Jakowski
2020-07-22 17:21 ` Klaus Jensen
2020-07-22 18:14 ` Andrzej Jakowski
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=20200715082106.GA530932@apples.localdomain \
--to=its@irrelevant.dk \
--cc=andrzej.jakowski@linux.intel.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).