Re: [RFC PATCH 1/9] cxl/acpi: Add an acpi_cxl module for the CXL interconnect

On Wed, 2020-11-11 at 07:10 +, Christoph Hellwig wrote: > On Tue, Nov 10, 2020 at 09:43:48PM -0800, Ben Widawsky wrote: > > +menuconfig CXL_BUS > > + tristate "CXL (Compute Express Link) Devices Support" > > + help > > + CXL is a bus that is electrically compatible with PCI-E, but layer

Re: [RFC PATCH 1/9] cxl/acpi: Add an acpi_cxl module for the CXL interconnect

On Wed, 2020-11-11 at 07:34 +, h...@infradead.org wrote: > On Wed, Nov 11, 2020 at 07:30:34AM +0000, Verma, Vishal L wrote: > > Hi Christpph, > > > > I thought 100 col. lines were acceptable now. > > Quote from the coding style document: > > "The pre

Re: [RFC PATCH 1/9] cxl/acpi: Add an acpi_cxl module for the CXL interconnect

On Mon, 2020-11-16 at 17:59 +, Jonathan Cameron wrote: > On Tue, 10 Nov 2020 21:43:48 -0800 > Ben Widawsky wrote: > > > From: Vishal Verma > > > > Add an acpi_cxl module to coordinate the ACPI portions of the CXL > > (Compute eXpress Link) interconnect. This driver binds to ACPI0017 > > obj

Re: [PATCH] ACPI: Replace HTTP links with HTTPS ones

On Fri, 2020-07-17 at 20:24 +0200, Alexander A. Klimov wrote: > Rationale: > Reduces attack surface on kernel devs opening the links for MITM > as HTTPS traffic is much harder to manipulate. > > Deterministic algorithm: > For each file: > If not .svg: > For each line: > If doesn't cont

Re: [PATCH v4 2/2] ACPICA: Preserve memory opregion mappings

On Mon, 2020-06-29 at 18:33 +0200, Rafael J. Wysocki wrote: > From: "Rafael J. Wysocki" > > The ACPICA's strategy with respect to the handling of memory mappings > associated with memory operation regions is to avoid mapping the > entire region at once which may be problematic at least in princip

[GIT PULL] libnvdimm fix for v5.9-rc5

Hi Linus, please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git tags/libnvdimm-fix-v5.9-rc5 ...to receive another fix for detection of DAX support for block devices. The previous fix in this area (merged in -rc3) was incomplete, and this should finally address all the

Re: [PATCH 3/6] libnvdimm/region: Register badblocks before namespaces

On Tue, 2019-06-11 at 16:25 -0700, Dan Williams wrote: > Namespace activation expects to be able to reference region badblocks. > The following warning sometimes triggers when asynchronous namespace > activation races in front of the completion of namespace probing. Move > all possible namespace pr

Re: [RESEND PATCH] nvdimm: fix some compilation warnings

On Wed, 2019-05-15 at 17:26 -0700, Dan Williams wrote: > On Wed, May 15, 2019 at 5:25 PM Verma, Vishal L > wrote: > > On Wed, 2019-05-15 at 16:25 -0700, Dan Williams wrote: > > > > diff --git a/drivers/nvdimm/btt.c b/drivers/nvdimm/btt.c > > > > ind

Re: [RESEND PATCH] nvdimm: fix some compilation warnings

On Wed, 2019-05-15 at 16:25 -0700, Dan Williams wrote: > > > diff --git a/drivers/nvdimm/btt.c b/drivers/nvdimm/btt.c > > index 4671776f5623..9f02a99cfac0 100644 > > --- a/drivers/nvdimm/btt.c > > +++ b/drivers/nvdimm/btt.c > > @@ -1269,11 +1269,9 @@ static int btt_read_pg(struct btt *btt, struct

Re: [PATCH] mm, memory-failure: clarify error message

On Thu, 2019-05-16 at 22:08 -0600, Jane Chu wrote: > Some user who install SIGBUS handler that does longjmp out > therefore keeping the process alive is confused by the error > message > "[188988.765862] Memory failure: 0x1840200: Killing >cellsrv:33395 due to hardware memory corruption" > Sl

Re: [RFC PATCH] x86, mce: change the mce notifier to 'blocking' from 'atomic'

On Thu, 2017-04-13 at 13:31 +0200, Borislav Petkov wrote: > On Thu, Apr 13, 2017 at 12:29:25AM +0200, Borislav Petkov wrote: > > On Wed, Apr 12, 2017 at 03:26:19PM -0700, Luck, Tony wrote: > > > We can futz with that and have them specify which chain (or both) > > > that they want to be added to. >

Re: [PATCH] block: hide badblocks attribute by default

On Thu, 2017-04-27 at 14:46 -0700, Dan Williams wrote: > Commit 99e6608c9e74 "block: Add badblock management for gendisks" > allowed for drivers like pmem and software-raid to advertise a list of > bad media areas. However, it inadvertently added a 'badblocks' to all > block devices. Lets clean thi

Re: [RFC PATCH] x86, mce: change the mce notifier to 'blocking' from 'atomic'

On Wed, 2017-04-12 at 22:22 +0200, Borislav Petkov wrote: > On Wed, Apr 12, 2017 at 01:59:03PM -0600, Vishal Verma wrote: > > I don't think we can do anything about the panic path errors. > > Then the fix should be a lot easier: > > --- > diff --git a/drivers/acpi/nfit/mce.c b/drivers/acpi/nfit/m

Re: [PATCH] libnvdimm: rework region badblocks clearing

On Mon, 2017-05-01 at 09:38 -0700, Dan Williams wrote: > On Mon, May 1, 2017 at 9:20 AM, Kani, Toshimitsu > wrote: > > On Mon, 2017-05-01 at 09:16 -0700, Dan Williams wrote: > > > On Mon, May 1, 2017 at 9:12 AM, Kani, Toshimitsu > > com> > > > wrote: > > > > On Mon, 2017-05-01 at 08:52 -0700, Dan

Re: [PATCH 1/2] nvdimm/btt: Fix memleaks in discover_arenas()

On Fri, 2025-05-16 at 13:13 +0800, Li Zhijian wrote: > kmemleak reported a memleak after the ndctl_test > unreferenced object 0x88800e6cf2c0 (size 32): >   comm "modprobe", pid 969, jiffies 4294698691 >   hex dump (first 32 bytes): >     03 00 00 00 a0 0a 00 00 00 b0 b4 00 00 c9 ff ff 

Re: [PATCH 2/2] nvdimm/btt: Fix memleaks in btt_init()

On Fri, 2025-05-16 at 13:13 +0800, Li Zhijian wrote: > Call free_arenas() to release the arena instances in btt->arena_list > in the error paths. > > Signed-off-by: Li Zhijian > --- >  drivers/nvdimm/btt.c | 12 >  1 file changed, 8 insertions(+), 4 deletions(-) > Reviewed-by: Vishal

<    1   2