From: Randy Dunlap <rdunlap@infradead.org>
To: Dave Jiang <dave.jiang@intel.com>,
vkoul@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dan.j.williams@intel.com, tony.luck@intel.com,
jing.lin@intel.com, ashok.raj@intel.com,
sanjay.k.kumar@intel.com, fenghua.yu@intel.com,
kevin.tian@intel.com
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/5] Add shared workqueue support for idxd driver
Date: Thu, 17 Sep 2020 16:56:03 -0700 [thread overview]
Message-ID: <3b4d8c50-8a82-9110-bc6c-ffb6b50e6c0c@infradead.org> (raw)
In-Reply-To: <84e1ec28-4a89-963a-49f6-3bbf1d276603@intel.com>
On 9/17/20 4:51 PM, Dave Jiang wrote:
>
>
> On 9/17/2020 4:43 PM, Randy Dunlap wrote:
>> Hi,
>>
>> On 9/17/20 2:15 PM, Dave Jiang wrote:
>>>
>>> ---
>>>
>>> Dave Jiang (5):
>>> x86/asm: move the raw asm in iosubmit_cmds512() to special_insns.h
>>> x86/asm: add enqcmds() to support ENQCMDS instruction
>>> dmaengine: idxd: add shared workqueue support
>>> dmaengine: idxd: clean up descriptors with fault error
>>> dmaengine: idxd: add ABI documentation for shared wq
>>>
>>
>> I don't see patch 3/5 in my inbox nor at https://lore.kernel.org/dmaengine/
>>
>> Did the email monster eat it?
>
> Grrrrrr looks like Intel email server ate it. Everyone on cc list got it. But does not look like it made it to any of the mailing lists. I'll resend 3/5.
Got it. Thanks.
>>
>> thanks.
>>
>>>
>>> Documentation/ABI/stable/sysfs-driver-dma-idxd | 14 ++
>>> arch/x86/include/asm/io.h | 46 +++++---
>>> arch/x86/include/asm/special_insns.h | 17 +++
>>> drivers/dma/Kconfig | 10 ++
>>> drivers/dma/idxd/cdev.c | 49 ++++++++
>>> drivers/dma/idxd/device.c | 91 ++++++++++++++-
>>> drivers/dma/idxd/dma.c | 9 --
>>> drivers/dma/idxd/idxd.h | 33 +++++-
>>> drivers/dma/idxd/init.c | 92 ++++++++++++---
>>> drivers/dma/idxd/irq.c | 143 ++++++++++++++++++++++--
>>> drivers/dma/idxd/registers.h | 14 ++
>>> drivers/dma/idxd/submit.c | 33 +++++-
>>> drivers/dma/idxd/sysfs.c | 127 +++++++++++++++++++++
>>> 13 files changed, 608 insertions(+), 70 deletions(-)
>>>
>>> --
>>>
>>
--
~Randy
prev parent reply other threads:[~2020-09-17 23:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 21:15 [PATCH v4 0/5] Add shared workqueue support for idxd driver Dave Jiang
2020-09-17 21:15 ` [PATCH v4 1/5] x86/asm: move the raw asm in iosubmit_cmds512() to special_insns.h Dave Jiang
2020-09-23 10:41 ` Borislav Petkov
2020-09-23 15:43 ` Dave Jiang
2020-09-23 16:00 ` David Laight
2020-09-17 21:15 ` [PATCH v4 2/5] x86/asm: add enqcmds() to support ENQCMDS instruction Dave Jiang
2020-09-23 11:08 ` Borislav Petkov
2020-09-23 15:47 ` Dave Jiang
2020-09-17 21:15 ` [PATCH v4 4/5] dmaengine: idxd: clean up descriptors with fault error Dave Jiang
2020-09-17 21:15 ` [PATCH v4 5/5] dmaengine: idxd: add ABI documentation for shared wq Dave Jiang
2020-09-17 23:43 ` [PATCH v4 0/5] Add shared workqueue support for idxd driver Randy Dunlap
2020-09-17 23:51 ` Dave Jiang
2020-09-17 23:56 ` Randy Dunlap [this message]
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=3b4d8c50-8a82-9110-bc6c-ffb6b50e6c0c@infradead.org \
--to=rdunlap@infradead.org \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=jing.lin@intel.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sanjay.k.kumar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vkoul@kernel.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).