From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Widawsky, Ben" <ben.widawsky@intel.com>,
"cbrowy@avery-design.com" <cbrowy@avery-design.com>
Cc: "Kelley, Sean V" <sean.v.kelley@intel.com>,
"Weiny, Ira" <ira.weiny@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [RFC PATCH 0/9] CXL 2.0 Support
Date: Fri, 4 Dec 2020 19:26:01 +0000 [thread overview]
Message-ID: <1878cd93df75dc8c1b35eab7b7aaaed243f9129e.camel@intel.com> (raw)
In-Reply-To: <20201204181217.n3cm7gqujaqlcp2h@intel.com>
On Fri, 2020-12-04 at 10:12 -0800, Ben Widawsky wrote:
> Hi Chris.
>
> On 20-12-04 12:40:03, Chris Browy wrote:
[..]
>
> > acpidump indicates the CXL0 and CXLM devices but no SRAT or HMAT tables are
> > in the dump which is curious.
>
> I don't typically use HMAT, but I do have an SRAT in mine, so that's strange.
> You should also have a CEDT.
>
I suspect an SRAT is only added if you have distinct numa nodes. Adding
a few '-numa node' bits to the qemu command line should be enough to
make that happen.
next prev parent reply other threads:[~2020-12-04 19:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FB00A034-7C6D-40B1-8452-318A3B052216@avery-design.com>
2020-12-04 17:40 ` [RFC PATCH 0/9] CXL 2.0 Support Chris Browy
2020-12-04 18:12 ` Ben Widawsky
2020-12-04 19:26 ` Verma, Vishal L [this message]
2020-12-04 19:45 ` Dan Williams
[not found] ` <B4FDE6CB-DA00-4F58-AA9F-F04E678E076B@avery-design.com>
2020-12-07 4:40 ` Chris Browy
2020-12-09 0:48 ` Ben Widawsky
2020-11-11 5:43 Ben Widawsky
2020-11-11 22:06 ` Ben Widawsky
2020-11-11 22:43 ` Bjorn Helgaas
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=1878cd93df75dc8c1b35eab7b7aaaed243f9129e.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=ben.widawsky@intel.com \
--cc=bhelgaas@google.com \
--cc=cbrowy@avery-design.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=sean.v.kelley@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 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.