From: Vinod Koul <vkoul@kernel.org>
To: Dave Jiang <dave.jiang@intel.com>
Cc: 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, David.Laight@aculab.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 3/5] dmaengine: idxd: Add shared workqueue support
Date: Mon, 5 Oct 2020 10:05:10 +0530 [thread overview]
Message-ID: <20201005043510.GE2968@vkoul-mobl> (raw)
In-Reply-To: <20200924180041.34056-4-dave.jiang@intel.com>
On 24-09-20, 11:00, Dave Jiang wrote:
> @@ -1154,6 +1268,8 @@ static struct attribute *idxd_wq_attributes[] = {
> &dev_attr_wq_mode.attr,
> &dev_attr_wq_size.attr,
> &dev_attr_wq_priority.attr,
> + &dev_attr_wq_block_on_fault.attr,
> + &dev_attr_wq_threshold.attr,
> &dev_attr_wq_type.attr,
> &dev_attr_wq_name.attr,
> &dev_attr_wq_cdev_minor.attr,
> @@ -1305,6 +1421,16 @@ static ssize_t clients_show(struct device *dev,
> }
> static DEVICE_ATTR_RO(clients);
>
> +static ssize_t pasid_enabled_show(struct device *dev,
> + struct device_attribute *attr, char *buf)
> +{
> + struct idxd_device *idxd =
> + container_of(dev, struct idxd_device, conf_dev);
> +
> + return sprintf(buf, "%u\n", device_pasid_enabled(idxd));
> +}
> +static DEVICE_ATTR_RO(pasid_enabled);
> +
> static ssize_t state_show(struct device *dev,
> struct device_attribute *attr, char *buf)
> {
> @@ -1424,6 +1550,7 @@ static struct attribute *idxd_device_attributes[] = {
> &dev_attr_gen_cap.attr,
> &dev_attr_configurable.attr,
> &dev_attr_clients.attr,
> + &dev_attr_pasid_enabled.attr,
No Documentation again for these new files! Please add them as well
--
~Vinod
next prev parent reply other threads:[~2020-10-05 4:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 18:00 [PATCH v6 0/5] Add shared workqueue support for idxd driver Dave Jiang
2020-09-24 18:00 ` [PATCH v6 1/5] x86/asm: Carve out a generic movdir64b() helper for general usage Dave Jiang
2020-09-24 18:33 ` Borislav Petkov
2020-09-24 18:00 ` [PATCH v6 2/5] x86/asm: Add enqcmds() to support ENQCMDS instruction Dave Jiang
2020-09-24 18:58 ` Borislav Petkov
2020-09-24 21:14 ` Dave Jiang
2020-09-24 22:09 ` David Laight
2020-09-24 18:00 ` [PATCH v6 3/5] dmaengine: idxd: Add shared workqueue support Dave Jiang
2020-10-05 4:35 ` Vinod Koul [this message]
2020-09-24 18:00 ` [PATCH v6 4/5] dmaengine: idxd: Clean up descriptors with fault error Dave Jiang
2020-10-05 4:42 ` Vinod Koul
2020-10-05 4:55 ` Dave Jiang
2020-10-05 5:45 ` Vinod Koul
2020-09-24 18:00 ` [PATCH v6 5/5] dmaengine: idxd: Add ABI documentation for shared wq Dave Jiang
2020-10-05 4:43 ` Vinod Koul
2020-09-24 21:32 ` [PATCH v6 0/5] Add shared workqueue support for idxd driver Dave Jiang
2020-09-24 21:51 ` Borislav Petkov
2020-09-24 22:05 ` Dave Jiang
2020-09-30 22:19 ` Dave Jiang
2020-10-01 4:29 ` Vinod Koul
2020-10-01 7:30 ` Borislav Petkov
2020-10-01 12:18 ` Jiang, Dave
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=20201005043510.GE2968@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=David.Laight@aculab.com \
--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 \
/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).