From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Moyer Subject: Re: [PATCH v3] libnvdimm, region: sysfs trigger for nvdimm_flush() Date: Thu, 27 Apr 2017 15:43:41 -0400 Message-ID: References: <149307780135.7155.11108531648914675756.stgit@dwillia2-desk3.amr.corp.intel.com> <149315140303.23340.14688142799059150805.stgit@dwillia2-desk3.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from mx1.redhat.com ([209.132.183.28]:38856 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S967863AbdD0Tnn (ORCPT ); Thu, 27 Apr 2017 15:43:43 -0400 In-Reply-To: (Dan Williams's message of "Thu, 27 Apr 2017 12:21:54 -0700") Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Dan Williams Cc: "linux-nvdimm@lists.01.org" , Masayoshi Mizuma , Linux ACPI , "linux-kernel@vger.kernel.org" Dan Williams writes: > We also still seem to need a discovery mechanism as I've had questions > about "how do I tell if my system supports deep flush?". That's where > sysfs is much better than an ioctl. The need for deep flush discovery > tips the scales, at least for me, to also do deep flush triggering > through the same interface. Return ENXIO or EOPNOTSUPP from the ioctl when it isn't supported? Cheers, Jeff