Linux CXL
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: Ravi Kanth <mvrravikanth@gmail.com>,
	Gregory Price <gregory.price@memverge.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	Sajjan Rao <sajjanr@gmail.com>
Subject: Re: Support for CXL v3.0 spec with QEMU
Date: Fri, 20 Oct 2023 13:38:22 -0700	[thread overview]
Message-ID: <6532e53ed63b0_21a97294d@iweiny-mobl.notmuch> (raw)
In-Reply-To: <CAEvOrRyMqBcv+6RseVS0x_6a3aJU82tjLJagmqCrgRebx5JaZg@mail.gmail.com>

Ravi Kanth wrote:
> Hi Jonathan / Gregory,
> Just wanted to touch base on below questions and if you have any
> inputs on the same. Thanks for your help.
> 
> Thanks
> Ravi
> 
> On Wed, Oct 18, 2023 at 4:00 PM Ravi Kanth <mvrravikanth@gmail.com> wrote:
> >
> > Hi Jonathan / Gregory,
> >
> > 1. Do we have the support in CXL driver to read the "Device status
> > registers" and specifically "Event status register" section 8.2.8.3
> > and 8.2.8.3.1?

Yes the upstream driver reads this when processing the Event interrupt
from the device.  Then it uses the value to chose which logs to read.

See cxl_event_thread() in the kernel source.

> > 2. If an interrupt is posted by the device firmware, how will user
> > space applications be notified ? Do we have an interface for the same
> > in CXL driver?

All events are reported through the trace infrastructure.

> >
> > If the above features are already supported in CXL driver, Can you
> > please point us to the sample code snippets to achieve the same?

ndctl has the ability to monitor these events and example C code in there.

See .../cxl/event_trace.c in the ndctl project.[1]

[1] https://github.com/pmem/ndctl

> >
> > Also does the switch cci function change part of the mainline?

I'm not sure I parse this question but I'm also not super familiar with
switch cci.  So I'll let Jonathan answer this.

Ira

> >
> > Thanks for your help in advance.
> >
> > Thanks
> > Ravi
> >

[snip]

  reply	other threads:[~2023-10-20 20:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 16:12 Support for CXL v3.0 spec with QEMU Ravi Kanth
2023-08-10 16:33 ` Jonathan Cameron
2023-08-10 16:40   ` Ravi Kanth
2023-08-11 12:04     ` Ravi Kanth
2023-08-11 13:52       ` Jonathan Cameron
2023-08-16 11:41         ` Ravi Kanth
2023-08-23 17:03           ` Jonathan Cameron
2023-09-01 14:03             ` Ravi Kanth
2023-09-01 14:18               ` Gregory Price
2023-09-01 14:37                 ` Ravi Kanth
2023-09-01 16:19                   ` Ravi Kanth
     [not found]                     ` <SJ0PR17MB5512449C5FFD76AD50B3D3AF83E4A@SJ0PR17MB5512.namprd17.prod.outlook.com>
2023-09-02 14:58                       ` Ravi Kanth
2023-10-18 10:30                         ` Ravi Kanth
2023-10-19 17:08                           ` Ravi Kanth
2023-10-20 20:38                             ` Ira Weiny [this message]
2023-10-22  6:45                               ` Ravi Kanth
2023-10-23 13:50                                 ` Jonathan Cameron
2023-10-26  1:52                                   ` Ravi Kanth
2023-10-26  8:59                                     ` Jonathan Cameron
2023-10-23 13:44                               ` Jonathan Cameron
2023-08-11 13:49     ` 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=6532e53ed63b0_21a97294d@iweiny-mobl.notmuch \
    --to=ira.weiny@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=gregory.price@memverge.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=mvrravikanth@gmail.com \
    --cc=sajjanr@gmail.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