From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM64:DMI: Add smbios/dmi support on arm64
Date: Thu, 5 Jun 2014 16:33:53 +0100 [thread overview]
Message-ID: <20140605153353.GC31564@leverpostej> (raw)
In-Reply-To: <538F34D0.5090905@linaro.org>
On Wed, Jun 04, 2014 at 04:01:36PM +0100, Yi Li wrote:
> Hi Mark,
>
> Please see the comments below:
>
> On Wednesday, June 04, 2014 09:32 PM, Mark Rutland wrote:
> > On Tue, Jun 03, 2014 at 04:57:13PM +0100, Yi Li wrote:
> >> Add smbios/dmi support on arm64 system, it depends on
> >> EFI boot.
> > And what exactly does this provide us with?
> >
> > What is exposed through SMBIOS/DMI, and why would I want to enable it?
> Yi: SMBIOS/DMI is one basic spec/feature for server product(like x86 and
> IA64).
> Many OEMs/ODMs hope to use ARM64 as server's processor.
> So we need to support SMBIOS on ARM64.
>
> SMBIOS mainly describes some hardware and software information for
> the system, like BIOS information
> CPU information, Memory information ,and so on. please refer to
> http://www.dmtf.org/standards/smbios
What information does it provide that is useful that we cannot get from
elsewhere?
What use case is enabled by having this support, other than being able
to tick a box that we have a feature we might not even need?
>
> >
> >> Signed-off-by: Yi Li <yi.li@linaro.org>
> >> ---
> >>
> >> Changes since v1:
> >> -Followed Ard Biesheuvel's suggestion to rebase the patch on
> >> Matt Fleming's arm64-efi branch.
> >>
> >> arch/arm64/Kconfig | 10 ++++++++++
> >> arch/arm64/include/asm/dmi.h | 28 ++++++++++++++++++++++++++++
> >> arch/arm64/kernel/setup.c | 2 ++
> >> 3 files changed, 40 insertions(+)
> >> create mode 100644 arch/arm64/include/asm/dmi.h
> >>
> >> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> >> index 6c71f12..13ee261 100644
> >> --- a/arch/arm64/Kconfig
> >> +++ b/arch/arm64/Kconfig
> >> @@ -294,6 +294,16 @@ config EFI
> >> allow the kernel to be booted as an EFI application. This
> >> is only useful on systems that have UEFI firmware.
> >>
> >> +config DMI
> >> + bool "Enable support for SMBIOS (DMI) tables"
> >> + depends on EFI
> >> + default y
> >> + help
> >> + This enables SMBIOS/DMI feature for systems.
> >> +
> >> + This option is only useful on systems that have UEFI firmware.
> >> + However, even with this option, the resultant kernel should
> >> + continue to boot on existing non-UEFI platforms.
> >> endmenu
> >>
> >> menu "Userspace binary formats"
> >> diff --git a/arch/arm64/include/asm/dmi.h b/arch/arm64/include/asm/dmi.h
> >> new file mode 100644
> >> index 0000000..f2198bf
> >> --- /dev/null
> >> +++ b/arch/arm64/include/asm/dmi.h
> >> @@ -0,0 +1,28 @@
> >> +/*
> >> + * arch/arm64/include/asm/dmi.h
> >> + *
> >> + * Copyright (C) 2013 Linaro Limited.
> >> + * Written by: Yi Li (yi.li at linaro.org)
> >> + *
> >> + * based on arch/ia64/include/asm/dmi.h
> >> + *
> >> + * This file is subject to the terms and conditions of the GNU General Public
> >> + * License. See the file "COPYING" in the main directory of this archive
> >> + * for more details.
> >> + */
> >> +
> >> +
> >> +#ifndef _ASM_DMI_H
> >> +#define _ASM_DMI_H 1
> >> +
> >> +#include <linux/slab.h>
> >> +#include <asm/io.h>
> > Shouldn't that be linux/efi.h?
> >
> > Why do we need asm/io.h?
> Yi: porting it from IA64 , so the io.h is not needed exactly!
> but slab.h is must included ,not efi.h (tested by compiling)
Below you refer to efi_lookup_mapped_addr, which (as far as I can tell)
is defined in efi.h. You might be getting lucky with users of
dmi_early_remap and dmi_remap having already incldued efi.h, but you
shouldn't rely on it.
If you make use of something, you should include the header that defines
it.
Cheers,
Mark.
> >> +
> >> +/* Use efi mappings for DMI */
> >> +#define dmi_early_remap(x, l) efi_lookup_mapped_addr(x)
> >> +#define dmi_early_unmap(x, l)
> >> +#define dmi_remap(x, l) efi_lookup_mapped_addr(x)
> >> +#define dmi_unmap(x)
> >> +#define dmi_alloc(l) kzalloc(l, GFP_ATOMIC)
> >> +
> >> +#endif
> > None of these seem to use anything from io.h directly.
> Yi: You are right , io.h doesn't need.
> > Cheers,
> > Mark.
>
>
next prev parent reply other threads:[~2014-06-05 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-03 15:57 [PATCH] ARM64:DMI: Add smbios/dmi support on arm64 Yi Li
2014-06-04 13:32 ` Mark Rutland
2014-06-04 15:01 ` Yi Li
2014-06-05 15:33 ` Mark Rutland [this message]
2014-06-06 1:57 ` 答复: " liyi 00215672
2014-06-06 12:58 ` Grant Likely
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=20140605153353.GC31564@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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