From: Jean Delvare <jdelvare@suse.de>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-kernel@vger.kernel.org,
Zhenzhong Duan <zhenzhong.duan@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] dmi_scan: Add comments on dmi_present() and the loop in dmi_scan_machine()
Date: Wed, 10 Jul 2013 18:23:35 +0200 [thread overview]
Message-ID: <1373473415.4399.53.camel@chaos.site> (raw)
In-Reply-To: <1373466723.24446.10.camel@deadeye.wl.decadent.org.uk>
Hi Ben,
Le Wednesday 10 July 2013 à 15:32 +0100, Ben Hutchings a écrit :
> My previous refactoring in commit 79bae42d51a5 resulted in slightly
> tricky code (though I think it's more elegant). Explain what it's
> doing.
You are being very nice to me, not sure I deserve it ;-)
> Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> ---
> drivers/firmware/dmi_scan.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/firmware/dmi_scan.c b/drivers/firmware/dmi_scan.c
> index b95159b..4fdb377 100644
> --- a/drivers/firmware/dmi_scan.c
> +++ b/drivers/firmware/dmi_scan.c
> @@ -419,6 +419,13 @@ static void __init dmi_format_ids(char *buf, size_t len)
> dmi_get_system_info(DMI_BIOS_DATE));
> }
>
> +/*
> + * Check for DMI/SMBIOS headers in the system firmware image. Any
> + * SMBIOS header must start 16 bytes before the DMI header, so take a
> + * 32 byte buffer and check for DMI at offset 16 and SMBIOS at offset
> + * 0. If the DMI header is present, set dmi_ver accordingly (SMBIOS
> + * takes precedence) and return 0. Otherwise return 1.
> + */
> static int __init dmi_present(const u8 *buf)
> {
> int smbios_ver;
> @@ -506,6 +513,13 @@ void __init dmi_scan_machine(void)
> if (p == NULL)
> goto error;
>
> + /*
> + * Iterate over all possible DMI header addresses q.
> + * Maintain the 32 bytes around q in buf. On the
> + * first iteration, substitute zero for the
> + * out-of-range bytes so there is no chance of falsely
> + * detecting an SMBIOS header.
> + */
> memset(buf, 0, 16);
> for (q = p; q < p + 0x10000; q += 16) {
> memcpy_fromio(buf + 16, q, 16);
>
Yes, I like it, good idea.
Reviewed-by: Jean Delvare <jdelvare@suse.de>
--
Jean Delvare
Suse L3
prev parent reply other threads:[~2013-07-10 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 14:32 Ben Hutchings
2013-07-10 16:23 ` Jean Delvare [this message]
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=1373473415.4399.53.camel@chaos.site \
--to=jdelvare@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenzhong.duan@oracle.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
all inboxes | Powered by JetHome®