public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
To: Simon Horman <horms@verge.net.au>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	vgoyal@redhat.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] sysfs: Add crash_notes_size to export percpu note size
Date: Fri, 29 Mar 2013 11:50:35 +0800	[thread overview]
Message-ID: <51550F8B.1000402@cn.fujitsu.com> (raw)
In-Reply-To: <5153FC27.70001@cn.fujitsu.com>

Hi, simon

I forgot to add your email in the CC, could you please help
reviewing this patch since I will send the kexec-tools patch
if this patch is accepted.

Thanks
Zhang

于 2013年03月28日 16:15, Zhang Yanfei 写道:
> For percpu notes, we are exporting only address and not size. So
> the userspace tool kexec-tools is putting an upper limit of 1024
> and putting the value in p_memsz and p_filesz fields. So the patch
> add the new sysfile crash_notes_size to export the exact percpu
> note size and let the kexec-tools parse it intead of using 1024.
> 
> The idea came from Vivek Goyal. And a later patch will be sent to
> kexec-tools to let it parse the size.
> 
> Cc: Greg KH <gregkh@linuxfoundation.org>
> Cc: "Eric W. Biederman" <ebiederm@xmission.com>
> Cc: Vivek Goyal <vgoyal@redhat.com>
> Signed-off-by: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
> ---
>  drivers/base/cpu.c |   14 ++++++++++++++
>  1 files changed, 14 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
> index fb10728..a55b590 100644
> --- a/drivers/base/cpu.c
> +++ b/drivers/base/cpu.c
> @@ -132,6 +132,17 @@ static ssize_t show_crash_notes(struct device *dev, struct device_attribute *att
>  	return rc;
>  }
>  static DEVICE_ATTR(crash_notes, 0400, show_crash_notes, NULL);
> +
> +static ssize_t show_crash_notes_size(struct device *dev,
> +				     struct device_attribute *attr,
> +				     char *buf)
> +{
> +	ssize_t rc;
> +
> +	rc = sprintf(buf, "%lu\n", sizeof(note_buf_t));
> +	return rc;
> +}
> +static DEVICE_ATTR(crash_notes_size, 0400, show_crash_notes_size, NULL);
>  #endif
>  
>  /*
> @@ -259,6 +270,9 @@ int __cpuinit register_cpu(struct cpu *cpu, int num)
>  #ifdef CONFIG_KEXEC
>  	if (!error)
>  		error = device_create_file(&cpu->dev, &dev_attr_crash_notes);
> +	if (!error)
> +		error = device_create_file(&cpu->dev,
> +					   &dev_attr_crash_notes_size);
>  #endif
>  	return error;
>  }


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  parent reply	other threads:[~2013-03-29  3:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-28  8:15 [PATCH 1/2] sysfs: Add crash_notes_size to export percpu note size Zhang Yanfei
2013-03-28  8:16 ` [PATCH 2/2] Documentation: Add ABI entry for crash_notes and crash_notes_size Zhang Yanfei
2013-03-29  4:05   ` Simon Horman
2013-03-29  3:50 ` Zhang Yanfei [this message]
2013-03-29  4:04   ` [PATCH 1/2] sysfs: Add crash_notes_size to export percpu note size Simon Horman

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=51550F8B.1000402@cn.fujitsu.com \
    --to=zhangyanfei@cn.fujitsu.com \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox