mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Buland Singh <bsingh@redhat.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: clemens@ladisch.de, arnd@arndb.de, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] hpet: Fix missing '=' character in the __setup() code of hpet_mmap_enable
Date: Thu, 20 Dec 2018 19:12:55 +0530	[thread overview]
Message-ID: <a9704df4-53ee-5b12-2ab1-477fb7e8f083@redhat.com> (raw)
In-Reply-To: <20181220122932.GB17138@kroah.com>

On 12/20/18 5:59 PM, Greg KH wrote:
> On Thu, Dec 20, 2018 at 05:35:24PM +0530, Buland Singh wrote:
>> Commit '3d035f580699 ("drivers/char/hpet.c: allow user controlled mmap for
>> user processes")' introduced a new kernel command line parameter hpet_mmap,
>> that is required to expose the memory map of the HPET registers to
>> user-space. Unfortunately the kernel command line parameter 'hpet_mmap' is
>> broken and never takes effect due to missing '=' character in the __setup()
>> code of hpet_mmap_enable.
>>
>> Before this patch:
>>
>> dmesg output with the kernel command line parameter hpet_mmap=1
>>
>> [    0.204152] HPET mmap disabled
>>
>> dmesg output with the kernel command line parameter hpet_mmap=0
>>
>> [    0.204192] HPET mmap disabled
>>
>> After this patch:
>>
>> dmesg output with the kernel command line parameter hpet_mmap=1
>>
>> [    0.203945] HPET mmap enabled
>>
>> dmesg output with the kernel command line parameter hpet_mmap=0
>>
>> [    0.204652] HPET mmap disabled
>>
>> Fixes: 3d035f580699 ("drivers/char/hpet.c: allow user controlled mmap for user processes")
>> Signed-off-by: Buland Singh <bsingh@redhat.com>
>> ---
>>   drivers/char/hpet.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/char/hpet.c b/drivers/char/hpet.c
>> index 4a22b4b41aef..9bffcd37cc7b 100644
>> --- a/drivers/char/hpet.c
>> +++ b/drivers/char/hpet.c
>> @@ -377,7 +377,7 @@ static __init int hpet_mmap_enable(char *str)
>>   	pr_info("HPET mmap %s\n", hpet_mmap_enabled ? "enabled" : "disabled");
>>   	return 1;
>>   }
>> -__setup("hpet_mmap", hpet_mmap_enable);
>> +__setup("hpet_mmap=", hpet_mmap_enable);

Hello Greag,

> This has _never_ worked?  Since 3.13?  

Yes, that's true :)

> Why not just remove the thing as it is obvious no one actually has ever used it.  > That would make the code even simpler :)

Data Plane Development Kit (DPDK)[1] provides API that requires the CONFIG_HPET_MMAP
kernel configuration option to be enabled[2]. Some end users might want to use the
HPET MMAP functionality within the application.
  
Regards,
Buland Singh

[1] https://www.dpdk.org
[2] https://doc.dpdk.org/guides-18.08/linux_gsg/enable_func.html









  reply	other threads:[~2018-12-20 13:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 12:05 Buland Singh
2018-12-20 12:29 ` Greg KH
2018-12-20 13:42   ` Buland Singh [this message]
2018-12-20 14:09     ` Greg KH
2018-12-21 12:18       ` Buland Singh
2018-12-21 12:46         ` Greg KH
2019-01-06 14:09           ` Buland Singh
2019-01-07 12:34             ` Prarit Bhargava

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=a9704df4-53ee-5b12-2ab1-477fb7e8f083@redhat.com \
    --to=bsingh@redhat.com \
    --cc=arnd@arndb.de \
    --cc=clemens@ladisch.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®