From: Fam Zheng <fam@euphon.net> To: Maxim Levitsky <mlevitsk@redhat.com> Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Jens Axboe <axboe@fb.com>, Alex Williamson <alex.williamson@redhat.com>, Keith Busch <keith.busch@intel.com>, Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>, Kirti Wankhede <kwankhede@nvidia.com>, "David S . Miller" <davem@davemloft.net>, Mauro Carvalho Chehab <mchehab+samsung@kernel.org>, Greg Kroah-Hartman <gregkh@linuxfoundation.org>, Wolfram Sang <wsa@the-dreams.de>, Nicolas Ferre <nicolas.ferre@microchip.com>, "Paul E . McKenney " <paulmck@linux.ibm.com>, Paolo Bonzini <pbonzini@redhat.com>, Liang Cunming <cunming.liang@intel.com>, Liu Changpeng <changpeng.liu@intel.com>, Amnon Ilan <ailan@redhat.com>, John Ferlan <jferlan@redhat.com> Subject: Re: [PATCH 4/9] nvme/pci: use the NVME_CTRL_SUSPENDED state Date: Wed, 20 Mar 2019 10:54:15 +0800 [thread overview] Message-ID: <20190320025415.bli42qmifuu5gxdm@deb> (raw) In-Reply-To: <20190319144116.400-5-mlevitsk@redhat.com> On Tue, 03/19 16:41, Maxim Levitsky wrote: > When enteriing low power state, the nvme Typo: "entering". > driver will now inform the core with the NVME_CTRL_SUSPENDED state > which will allow mdev driver to act on this information [snip] Fam
WARNING: multiple messages have this Message-ID (diff)
From: fam@euphon.net (Fam Zheng) Subject: [PATCH 4/9] nvme/pci: use the NVME_CTRL_SUSPENDED state Date: Wed, 20 Mar 2019 10:54:15 +0800 [thread overview] Message-ID: <20190320025415.bli42qmifuu5gxdm@deb> (raw) In-Reply-To: <20190319144116.400-5-mlevitsk@redhat.com> On Tue, 03/19 16:41, Maxim Levitsky wrote: > When enteriing low power state, the nvme Typo: "entering". > driver will now inform the core with the NVME_CTRL_SUSPENDED state > which will allow mdev driver to act on this information [snip] Fam
next prev parent reply other threads:[~2019-03-20 3:12 UTC|newest] Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-19 14:41 No subject Maxim Levitsky 2019-03-19 14:41 ` (unknown) Maxim Levitsky 2019-03-19 14:41 ` [PATCH 1/9] vfio/mdev: add .request callback Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` [PATCH 2/9] nvme/core: add some more values from the spec Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` [PATCH 3/9] nvme/core: add NVME_CTRL_SUSPENDED controller state Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` [PATCH 4/9] nvme/pci: use the NVME_CTRL_SUSPENDED state Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-20 2:54 ` Fam Zheng [this message] 2019-03-20 2:54 ` Fam Zheng 2019-03-19 14:41 ` [PATCH 5/9] nvme/pci: add known admin effects to augument admin effects log page Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` [PATCH 6/9] nvme/pci: init shadow doorbell after each reset Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` [PATCH 7/9] nvme/core: add mdev interfaces Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-20 11:46 ` Stefan Hajnoczi 2019-03-20 11:46 ` Stefan Hajnoczi 2019-03-20 11:46 ` Stefan Hajnoczi 2019-03-20 12:50 ` Maxim Levitsky 2019-03-20 12:50 ` Maxim Levitsky 2019-03-20 12:50 ` Maxim Levitsky 2019-03-19 14:41 ` [PATCH 8/9] nvme/core: add nvme-mdev core driver Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` [PATCH 9/9] nvme/pci: implement the mdev external queue allocation interface Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:41 ` Maxim Levitsky 2019-03-19 14:58 ` [PATCH 0/9] RFC: NVME VFIO mediated device Maxim Levitsky 2019-03-19 14:58 ` Maxim Levitsky 2019-03-25 18:52 ` [PATCH 0/9] RFC: NVME VFIO mediated device [BENCHMARKS] Maxim Levitsky 2019-03-25 18:52 ` Maxim Levitsky 2019-03-26 9:38 ` Stefan Hajnoczi 2019-03-26 9:38 ` Stefan Hajnoczi 2019-03-26 9:38 ` Stefan Hajnoczi 2019-03-26 9:50 ` Maxim Levitsky 2019-03-26 9:50 ` Maxim Levitsky 2019-03-26 9:50 ` Maxim Levitsky 2019-03-19 15:22 ` your mail Keith Busch 2019-03-19 15:22 ` Keith Busch 2019-03-19 15:22 ` Keith Busch 2019-03-19 23:49 ` Chaitanya Kulkarni 2019-03-19 23:49 ` Chaitanya Kulkarni 2019-03-19 23:49 ` Chaitanya Kulkarni 2019-03-20 16:44 ` Maxim Levitsky 2019-03-20 16:44 ` Maxim Levitsky 2019-03-20 16:44 ` Maxim Levitsky 2019-03-20 16:30 ` Maxim Levitsky 2019-03-20 16:30 ` Maxim Levitsky 2019-03-20 16:30 ` Maxim Levitsky 2019-03-20 17:03 ` Keith Busch 2019-03-20 17:03 ` Keith Busch 2019-03-20 17:03 ` Keith Busch 2019-03-20 17:33 ` Maxim Levitsky 2019-03-20 17:33 ` Maxim Levitsky 2019-03-20 17:33 ` Maxim Levitsky 2019-04-08 10:04 ` Maxim Levitsky 2019-04-08 10:04 ` Maxim Levitsky 2019-03-20 11:03 ` Felipe Franciosi 2019-03-20 11:03 ` Re: Felipe Franciosi 2019-03-20 11:03 ` No subject Felipe Franciosi 2019-03-20 19:08 ` Maxim Levitsky 2019-03-20 19:08 ` Re: Maxim Levitsky 2019-03-20 19:08 ` No subject Maxim Levitsky 2019-03-21 16:12 ` Stefan Hajnoczi 2019-03-21 16:12 ` Re: Stefan Hajnoczi 2019-03-21 16:12 ` No subject Stefan Hajnoczi 2019-03-21 16:21 ` Keith Busch 2019-03-21 16:21 ` Re: Keith Busch 2019-03-21 16:21 ` No subject Keith Busch 2019-03-21 16:41 ` Felipe Franciosi 2019-03-21 16:41 ` Re: Felipe Franciosi 2019-03-21 16:41 ` No subject Felipe Franciosi 2019-03-21 17:04 ` Maxim Levitsky 2019-03-21 17:04 ` Re: Maxim Levitsky 2019-03-21 17:04 ` No subject Maxim Levitsky 2019-03-22 7:54 ` Felipe Franciosi 2019-03-22 7:54 ` Re: Felipe Franciosi 2019-03-22 7:54 ` No subject Felipe Franciosi 2019-03-22 10:32 ` Maxim Levitsky 2019-03-22 10:32 ` Re: Maxim Levitsky 2019-03-22 10:32 ` No subject Maxim Levitsky 2019-03-22 15:30 ` Keith Busch 2019-03-22 15:30 ` Re: Keith Busch 2019-03-22 15:30 ` No subject Keith Busch 2019-03-25 15:44 ` Felipe Franciosi 2019-03-25 15:44 ` Re: Felipe Franciosi 2019-03-25 15:44 ` No subject Felipe Franciosi 2019-03-20 15:08 ` [PATCH 0/9] RFC: NVME VFIO mediated device Bart Van Assche 2019-03-20 15:08 ` Bart Van Assche 2019-03-20 16:48 ` Maxim Levitsky 2019-03-20 16:48 ` Maxim Levitsky 2019-03-20 15:28 ` Bart Van Assche 2019-03-20 15:28 ` Bart Van Assche 2019-03-20 16:42 ` Maxim Levitsky 2019-03-20 16:42 ` Maxim Levitsky 2019-03-20 17:03 ` Alex Williamson 2019-03-20 17:03 ` Alex Williamson 2019-03-20 17:03 ` Alex Williamson 2019-03-21 16:13 ` your mail Stefan Hajnoczi 2019-03-21 16:13 ` Stefan Hajnoczi 2019-03-21 16:13 ` Stefan Hajnoczi 2019-03-21 17:07 ` Maxim Levitsky 2019-03-21 17:07 ` Maxim Levitsky 2019-03-21 17:07 ` Maxim Levitsky 2019-03-25 16:46 ` Stefan Hajnoczi 2019-03-25 16:46 ` Stefan Hajnoczi 2019-03-25 16:46 ` Stefan Hajnoczi
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=20190320025415.bli42qmifuu5gxdm@deb \ --to=fam@euphon.net \ --cc=ailan@redhat.com \ --cc=alex.williamson@redhat.com \ --cc=axboe@fb.com \ --cc=changpeng.liu@intel.com \ --cc=cunming.liang@intel.com \ --cc=davem@davemloft.net \ --cc=gregkh@linuxfoundation.org \ --cc=hch@lst.de \ --cc=jferlan@redhat.com \ --cc=keith.busch@intel.com \ --cc=kvm@vger.kernel.org \ --cc=kwankhede@nvidia.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-nvme@lists.infradead.org \ --cc=mchehab+samsung@kernel.org \ --cc=mlevitsk@redhat.com \ --cc=nicolas.ferre@microchip.com \ --cc=paulmck@linux.ibm.com \ --cc=pbonzini@redhat.com \ --cc=sagi@grimberg.me \ --cc=wsa@the-dreams.de \ /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: linkBe 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.