On Thu, Jan 19, 2023 at 06:48:11AM -0500, Michael S. Tsirkin wrote:
> >
> > I clearly need to run some more rests as not seen this issue (and I've
> > had a couple of reports of it now). I guess I never tend to be running
> > a completely clean tree on either side + testing is mostly on arm64
> >
On Thu, Jan 19, 2023 at 10:19:46AM +, Jonathan Cameron wrote:
> Even if everything else worked, it will currently fail because of the
> issue with pass through decoders.
> (Kernel assumes always pass through for single rp, qemu assumes never
> pass through - both are valid under spec).
> Add a
On Wed, 18 Jan 2023 14:31:53 -0500
Gregory Price wrote:
> I apparently forgot an intro lol
>
> I tested the DOE linux branch with the 2023-1-11 QEMU branch with both
> volatile, non-volatile, and "legacy" (pre-my-patch) non-volatile mode.
>
> 1) *In volatile mode, there are no stack traces pres
On Thu, 19 Jan 2023 06:48:11 -0500
"Michael S. Tsirkin" wrote:
> On Thu, Jan 19, 2023 at 10:19:46AM +, Jonathan Cameron wrote:
> > On Wed, 18 Jan 2023 14:22:08 -0500
> > Gregory Price wrote:
> >
> > > 1) No stack traces present
> > > 2) Device usage appears to work, but cxl-cli fails to c
On Thu, Jan 19, 2023 at 10:19:46AM +, Jonathan Cameron wrote:
> On Wed, 18 Jan 2023 14:22:08 -0500
> Gregory Price wrote:
>
> > 1) No stack traces present
> > 2) Device usage appears to work, but cxl-cli fails to create a region, i
> > haven't checked why yet (also tried ndctl-75, same result
On Wed, 18 Jan 2023 14:22:08 -0500
Gregory Price wrote:
> 1) No stack traces present
> 2) Device usage appears to work, but cxl-cli fails to create a region, i
> haven't checked why yet (also tried ndctl-75, same results)
> 3) There seems to be some other regression with the cxl_pmem_init
> routi
I apparently forgot an intro lol
I tested the DOE linux branch with the 2023-1-11 QEMU branch with both
volatile, non-volatile, and "legacy" (pre-my-patch) non-volatile mode.
1) *In volatile mode, there are no stack traces present (during boot*)
On Wed, Jan 18, 2023 at 02:22:08PM -0500, Gregory
1) No stack traces present
2) Device usage appears to work, but cxl-cli fails to create a region, i
haven't checked why yet (also tried ndctl-75, same results)
3) There seems to be some other regression with the cxl_pmem_init
routine, because I get a stack trace in this setup regardless of whethe
On Fri, Jan 13, 2023 at 02:45:11PM +, Jonathan Cameron wrote:
> On Fri, 13 Jan 2023 14:40:26 + Jonathan Cameron
> wrote:
> > On Fri, 13 Jan 2023 09:19:59 -0500 Gregory Price
> > wrote:
> > > On Fri, Jan 13, 2023 at 09:12:13AM +, Jonathan Cameron wrote:
> > > > Just to check, are t
On Fri, Jan 13, 2023 at 09:12:13AM +, Jonathan Cameron wrote:
>
> Just to check, are these different from the on stack problem you reported
> previously? Doesn't look like the fix for that has made it upstream yet.
>
> What kernel are you running?
>
>
The prior issue I saw was related to
On Fri, Jan 13, 2023 at 04:12:06PM +0100, Lukas Wunner wrote:
> On Fri, Jan 13, 2023 at 02:45:11PM +, Jonathan Cameron wrote:
> > On Fri, 13 Jan 2023 14:40:26 + Jonathan Cameron
> > wrote:
> > > On Fri, 13 Jan 2023 09:19:59 -0500 Gregory Price
> > > wrote:
> > > > On Fri, Jan 13, 2023 a
On Fri, 13 Jan 2023 09:19:59 -0500
Gregory Price wrote:
> On Fri, Jan 13, 2023 at 09:12:13AM +, Jonathan Cameron wrote:
> >
> > Just to check, are these different from the on stack problem you reported
> > previously? Doesn't look like the fix for that has made it upstream yet.
> >
> > Wha
On Fri, 13 Jan 2023 14:40:26 +
Jonathan Cameron wrote:
> On Fri, 13 Jan 2023 09:19:59 -0500
> Gregory Price wrote:
>
> > On Fri, Jan 13, 2023 at 09:12:13AM +, Jonathan Cameron wrote:
> > >
> > > Just to check, are these different from the on stack problem you reported
> > > previousl
Ah I see, i forgot about that one. Give me a bit and I'll see if it is the
same issue.
On Fri, Jan 13, 2023 at 9:41 AM Jonathan Cameron <
jonathan.came...@huawei.com> wrote:
> On Fri, 13 Jan 2023 09:19:59 -0500
> Gregory Price wrote:
>
> > On Fri, Jan 13, 2023 at 09:12:13AM +, Jonathan Came
On Thu, 12 Jan 2023 17:46:27 -0500
Gregory Price wrote:
> On Thu, Jan 12, 2023 at 05:21:30PM +, Jonathan Cameron wrote:
> > On Thu, 12 Jan 2023 10:39:17 -0500
> > Gregory Price wrote:
> >
> > > On Wed, Jan 11, 2023 at 02:24:32PM +, Jonathan Cameron via wrote:
> > > > Gregory's patch
On Thu, Jan 12, 2023 at 05:21:30PM +, Jonathan Cameron wrote:
> On Thu, 12 Jan 2023 10:39:17 -0500
> Gregory Price wrote:
>
> > On Wed, Jan 11, 2023 at 02:24:32PM +, Jonathan Cameron via wrote:
> > > Gregory's patches were posted as part of his work on adding volatile
> > > support.
> >
On Thu, 12 Jan 2023 10:39:17 -0500
Gregory Price wrote:
> On Wed, Jan 11, 2023 at 02:24:32PM +, Jonathan Cameron via wrote:
> > Gregory's patches were posted as part of his work on adding volatile
> > support.
> > https://lore.kernel.org/linux-cxl/20221006233702.18532-1-gregory.pr...@memverg
On Wed, Jan 11, 2023 at 02:24:32PM +, Jonathan Cameron via wrote:
> Gregory's patches were posted as part of his work on adding volatile support.
> https://lore.kernel.org/linux-cxl/20221006233702.18532-1-gregory.pr...@memverge.com/
> https://lore.kernel.org/linux-cxl/20221128150157.97724-2-gre
A small collection of misc fixes and tidying up pulled out from various
series. I've pulled this to the top of my queue of CXL related work
as they stand fine on their own and it will reduce the noise in
the larger patch sets if these go upstream first.
Gregory's patches were posted as part of his
19 matches
Mail list logo
