From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Gregory Price <gregory.price@memverge.com>
Cc: Dan Williams <dan.j.williams@intel.com>, <linux-cxl@vger.kernel.org>
Subject: Re: [GIT preview] for-6.3/cxl-ram-region
Date: Tue, 31 Jan 2023 14:56:16 +0000 [thread overview]
Message-ID: <20230131145616.00006c9c@Huawei.com> (raw)
In-Reply-To: <Y9fS+vJft+P0FYWQ@memverge.com>
On Mon, 30 Jan 2023 09:23:54 -0500
Gregory Price <gregory.price@memverge.com> wrote:
> On Thu, Jan 26, 2023 at 07:34:24PM +0000, Jonathan Cameron wrote:
> > Looks like decoders are programmed correctly as I can read and write from
> > the HPA using devmem2.
> >
> > This is against http://gitlab.com/jic23/qemu cxl-2023-01-26 which has been
> >
>
> Johnathan, can you explain how you're accessing the memory? I don't
> quite follow.
Command sequence is pretty similar to yours (not checked it's identical)
and once commit is done, using a version of devmem2 (not sure it was this one)
https://github.com/hackndev/tools/blob/master/devmem2.c
(if you want 64 bit read / write add the obvious additional parameter ;)
with appropriately loose kernel configuration that /dev/mem works
Then run that against addresses starting at the bottom of the CFMWS
HPA range to read and write. It's a hack but proves the routing etc
is all setup correctly.
I had this lying around from testing the region setup code when it
was in a similar partial state to this support.
Jonathan
>
> Extra Notes
> 1) Tested against Jonathan's QEMU 01-26 branch above
> 2) Tested w/ the Linux preview branch rebased on top of the DOE fixes
> that were causing other bugs.
next prev parent reply other threads:[~2023-01-31 14:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 6:25 [GIT preview] for-6.3/cxl-ram-region Dan Williams
2023-01-26 6:29 ` Dan Williams
2023-01-26 18:50 ` Jonathan Cameron
2023-01-26 19:34 ` Jonathan Cameron
2023-01-30 14:16 ` Gregory Price
2023-01-30 20:10 ` Dan Williams
2023-01-30 20:58 ` Gregory Price
2023-01-30 23:18 ` Dan Williams
2023-01-30 22:00 ` Gregory Price
2023-01-31 2:00 ` Gregory Price
2023-01-31 16:56 ` Dan Williams
2023-01-31 17:59 ` Verma, Vishal L
2023-01-31 19:03 ` Gregory Price
2023-01-31 19:46 ` Verma, Vishal L
2023-01-31 20:24 ` Verma, Vishal L
2023-01-31 23:03 ` Gregory Price
2023-01-31 23:17 ` Gregory Price
2023-01-31 23:50 ` Fan Ni
2023-02-01 5:29 ` Gregory Price
2023-02-01 21:16 ` Gregory Price
2023-02-02 1:06 ` Gregory Price
2023-02-02 16:03 ` Jonathan Cameron
2023-02-01 22:05 ` Gregory Price
2023-02-02 18:13 ` Jonathan Cameron
2023-02-02 0:43 ` Gregory Price
2023-02-02 18:18 ` Dan Williams
2023-02-02 0:44 ` Gregory Price
2023-02-07 16:31 ` Jonathan Cameron
2023-01-30 14:23 ` Gregory Price
2023-01-31 14:56 ` Jonathan Cameron [this message]
2023-01-31 17:34 ` Gregory Price
2023-01-26 22:05 ` Gregory Price
2023-01-26 22:20 ` Dan Williams
2023-02-04 2:36 ` Dan Williams
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=20230131145616.00006c9c@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=gregory.price@memverge.com \
--cc=linux-cxl@vger.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 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.