From: Kevin Wolf <kwolf@redhat.com>
To: Shimi Gersner <gersner@gmail.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Keith Busch <keith.busch@intel.com>,
Max Reitz <mreitz@redhat.com>, David Sariel <davidsa@openu.ac.il>
Subject: Re: [Qemu-devel] [PATCH 1/5] nvme: PCI/e configuration from specification
Date: Thu, 12 Jul 2018 13:47:33 +0200 [thread overview]
Message-ID: <20180712114733.GE4541@localhost.localdomain> (raw)
In-Reply-To: <20180622112237.2131-1-gersner@gmail.com>
Am 22.06.2018 um 13:22 hat Shimi Gersner geschrieben:
> PCI/e configuration currently does not meets specifications.
>
> Patch includes various configuration changes to support specifications
> - BAR2 to return zero when read and CMD.IOSE is not set.
> - Expose NVME configuration through IO space (Optional).
> - PCI Power Management v1.2.
> - PCIe Function Level Reset.
> - Disable QEMUs default use of PCIe Link Status (DLLLA).
> - PCIe missing AOC compliance flag.
> - Mask PCIe End-to-End TLP as RO (Unspecified by specification).
>
> Change-Id: I9057f56266db16b013fa194730c998d4779cede3
What is the meaning of this Change-Id tag?
> Signed-off-by: Shimi Gersner <gersner@gmail.com>
Keith, can you have a look at this series?
Kevin
next prev parent reply other threads:[~2018-07-12 11:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 11:22 [Qemu-devel] [PATCH 1/5] nvme: PCI/e configuration from specification Shimi Gersner
2018-06-22 11:22 ` [Qemu-devel] [PATCH 2/5] nvme: CQ/SQ proper validation & status code Shimi Gersner
2018-06-22 11:22 ` [Qemu-devel] [PATCH 3/5] nvme: Proper state handling on enable/disable Shimi Gersner
2018-06-22 11:22 ` [Qemu-devel] [PATCH 4/5] nvme: Fix phantom irq raise Shimi Gersner
2018-06-22 11:22 ` [Qemu-devel] [PATCH 5/5] nvme: Missing MSI message upon partial CQ read Shimi Gersner
2018-07-12 11:47 ` Kevin Wolf [this message]
2018-07-13 7:40 ` [Qemu-devel] [PATCH 1/5] nvme: PCI/e configuration from specification David Sariel
2018-07-15 6:20 ` Daniel Verkamp
2018-08-26 21:49 ` Gersner
2018-08-30 15:45 ` Daniel Verkamp
2018-09-12 19:53 ` Gersner
2018-09-12 21:21 ` Eric Blake
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=20180712114733.GE4541@localhost.localdomain \
--to=kwolf@redhat.com \
--cc=davidsa@openu.ac.il \
--cc=gersner@gmail.com \
--cc=keith.busch@intel.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 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.