From: ajay.opensrc <ajay.opensrc@micron.com>
To: Jonathan Cameron <Jonathan.Cameron@Huawei.com>,
Srinivasulu Opensrc <sthanneeru.opensrc@micron.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"john@jagalactic.com" <john@jagalactic.com>,
Eishan Mirakhur <emirakhur@micron.com>,
Ravis OpenSrc <Ravis.OpenSrc@micron.com>,
Srinivasulu Thanneeru <sthanneeru@micron.com>,
Ajay Joshi <ajayjoshi@micron.com>
Subject: Re: [EXT] RE: [PATCH v3 0/2] Add log related mailbox commands
Date: Wed, 24 Apr 2024 02:13:59 +0000 [thread overview]
Message-ID: <d3314d138a494a08b65bdf5fd4b034d0@micron.com> (raw)
In-Reply-To: <8b5fa16f05cb4fde87441ffd81552b38@micron.com>
> Jonathan Cameron <Jonathan.Cameron@Huawei.com> wrote:
> > Srinivasulu Opensrc <sthanneeru.opensrc@micron.com> wrote:
> >
>
> > > >-----Original Message-----
> > > >From: Dan Williams <dan.j.williams@intel.com>
> > > >Sent: Wednesday, March 27, 2024 5:07 AM
> > > >To: Srinivasulu Opensrc <sthanneeru.opensrc@micron.com>; linux-
> > > >cxl@vger.kernel.org
> > > >Cc: Jonathan.Cameron@huawei.com; dan.j.williams@intel.com;
> > > >john@jagalactic.com; Eishan Mirakhur <emirakhur@micron.com>; Ajay
> > > >Joshi <ajayjoshi@micron.com>; Ravis OpenSrc
> > > ><Ravis.OpenSrc@micron.com>; Srinivasulu Thanneeru
> > > ><sthanneeru@micron.com>
> > > >Subject: [EXT] RE: [PATCH v3 0/2] Add log related mailbox commands
> > > >
> > > >CAUTION: EXTERNAL EMAIL. Do not click links or open attachments
> > > >unless you recognize the sender and were expecting this message.
> > > >
> > > >
> > > >sthanneeru.opensrc@ wrote:
> > > >> From: Srinivasulu Thanneeru <sthanneeru.opensrc@micron.com>
> > > >>
> > > >> Add support to expose following mailbox commands to userspace for
> > > >> clearing and populating the Vendor debug log in certain
> > > >> scenarios, allowing for the aggregation of results over time.
> > > >>
> > > >> 1. CXL r3.1 8.2.9.5.3 Get Log Capabilities.
> > > >> 2. CXL r3.1 8.2.9.5.4 Clear Log commands.
> > > >> 3. CXL r3.1 8.2.9.5.6 Get Supported Logs Sub-List.
> > > >>
> > > >> ---
> > > >> Changes in v3:
> > > >> - 'Component State Dump log' has several caveats for ioctl()
> > > >> not being a suitable ABI as pointed in v2.(Dan Williams)
> > > >> - Remove Component State Dump from Clear log filter.
> > > >> - Implement a seperate patch(yet to do) to address issues as
> > > >> pointed in
> > v2.
> > > >
> > > >Circling back to this question... I had overlooked the fact that in
> > > >v3.1 the "Request Abort Background Operation" command was added
> > (8.2.9.1.5).
> > > >With that the kernel can safely support background commands with
> > > >indefinite residency. So as long as the device supports that
> > > >command and advertises that Log populate requests can be cancelled
> > > >then we can build a facility to cancel any user-submitted
> > > >background commands when a kernel internal need for the background
> command slot arises.
> > >
> > > I don't have the access to test "Request Abort Background Operation."
> > > Previously, we posted RFC for default time for background operations.
> > >
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore
> >
> %2F&data=05%7C02%7Cajayjoshi%40micron.com%7Cf8029f5d498b4f0e64fb
> 08dc58
> >
> 387ed0%7Cf38a5ecd28134862b11bac1d563c806f%7C0%7C0%7C6384822468
> 83954825
> >
> %7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiL
> CJBTiI6I
> >
> k1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Lv366Ff7nRD9zI6F0AQC
> e%2F9f%2F
> > QwNiL%2FCpND2cpfX6E0%3D&reserved=0
> > > .kernel.org%2Flinux-mm%2F20240207105349.301-1-
> > sthanneeru.opensrc%40mic
> > >
> > ron.com%2F&data=05%7C02%7Cajayjoshi%40micron.com%7Cabe61f69d40
> > 2460e2f2
> > >
> > b08dc55964860%7Cf38a5ecd28134862b11bac1d563c806f%7C0%7C0%7C
> > 63847935119
> > >
> > 7749869%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoi
> > V2luMzIiLC
> > >
> > JBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=QyxjJi2iLMTSTl
> > R46rv9k5
> > > U%2FDZVrKruaaunew8HMR9E%3D&reserved=0
> > >
> > > Could you please guide me on how to proceed with this current patch
> > series?
> >
> > Whilst QEMU emulation doesn't yet support background command
> aborting,
> > it wouldn't be that hard to add and would provide a route to test this
> > functionality.
> > We've done similar in a few other cases where no one had any hardware
> yet.
> >
> > Of course that might not help you if you have silicon that doesn't
> > implement it but I agree with Dan that it is a lot less problematic to
> > allow for unbounded background ops if we can stop them for other urgent
> activity.
> >
>
> Thanks Jonathan and Dan. Agree with you on the background command
> handling.
> The series which Srini (sthanneeru.opensrc) has submitted has 2 patches:
> cxl/mbox: Add Get Log Capabilities and Get Supported Logs Sub-List
> commands
> cxl/mbox: Add Clear Log mailbox command
> The commands in these patches(opcodes: 0402h, 0403h, 0405h) don't seem
> to have any background handling as of 3.1.
> Do you think these patches seem ok or do you feel something is missing
> here?
>
Any input or review comment here would be highly appreciated.
>
> Ajay
>
> > Jonathan
next prev parent reply other threads:[~2024-04-24 2:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 1:58 [EXT] RE: [PATCH v3 0/2] Add log related mailbox commands ajay.opensrc
2024-04-24 2:13 ` ajay.opensrc [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-13 7:12 sthanneeru.opensrc
2024-03-26 23:37 ` Dan Williams
2024-04-01 6:03 ` [EXT] " Srinivasulu Opensrc
2024-04-05 17:31 ` Jonathan Cameron
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=d3314d138a494a08b65bdf5fd4b034d0@micron.com \
--to=ajay.opensrc@micron.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=Ravis.OpenSrc@micron.com \
--cc=ajayjoshi@micron.com \
--cc=dan.j.williams@intel.com \
--cc=emirakhur@micron.com \
--cc=john@jagalactic.com \
--cc=linux-cxl@vger.kernel.org \
--cc=sthanneeru.opensrc@micron.com \
--cc=sthanneeru@micron.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