rence the new location of the
> description in xive-regs.h
>
> Signed-off-by: Jordan Niethe
Acked-by: Stewart Smith
--
Stewart Smith
OPAL Architect, IBM.
Nishka Dasgupta writes:
> Each iteration of for_each_child_of_node puts the previous node, but
This is for_each_compatible_node.
otherwise looks okay,
Acked-by: Stewart Smith
--
Stewart Smith
OPAL Architect, IBM.
oundation; either version
> + * 2 of the License, or (at your option) any later version.
> + */
This file takes a bunch of code from fadump.c, which has the (C) header
showing (C) 2011, and author of Mahesh. We should probably preserve that
--
Stewart Smith
OPAL Architect, IBM.
off-by: Michael Neuling
Acked-by: Stewart Smith
--
Stewart Smith
OPAL Architect, IBM.
Michael Ellerman writes:
> Stewart Smith writes:
>> On my two socket POWER9 system (powernv) with 842 zwap set up, I
>> recently got a crash with the Ubuntu kernel (I haven't tried with
>> upstream, and this is the first time the system has died like this, so
>>
ash looks like this failure)?
--
Stewart Smith
OPAL Architect, IBM.
Oliver writes:
> On Tue, May 28, 2019 at 1:29 PM Stewart Smith wrote:
>>
>> If the previous comment made sense, continue debugging or call your
>> doctor immediately.
>>
>> Signed-off-by: Stewart Smith
>> ---
>> arch/powerpc/platforms/powernv
If the previous comment made sense, continue debugging or call your
doctor immediately.
Signed-off-by: Stewart Smith
---
arch/powerpc/platforms/powernv/eeh-powernv.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/eeh-powernv.c
b/arch
-off-by: Stewart Smith
---
arch/powerpc/platforms/powernv/opal.c | 23 +++
1 file changed, 15 insertions(+), 8 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/opal.c
b/arch/powerpc/platforms/powernv/opal.c
index f2b063b027f0..89b6ddc3ed38 100644
--- a/arch/powerpc
ices is still a little uncommon.
A 4 socket POWER8 or POWER9 can easily be that large, and a small test
kernel/userspace will boot in ~2.5-4 seconds. So it's possible that
the device tree fetch could be surprisingly non-trivial percentage of boot
time at least on some machines.
--
Stewart Smith
OPAL Architect, IBM.
Carol L Soto
>> Suggested-by: Carol L Soto
>> Signed-off-by: Stewart Smith
>> Signed-off-by: Joel Stanley
>
> Fixes: cbc39809a398 ("powerpc/configs: Update skiroot defconfig")
>
> ?
Yes.
--
Stewart Smith
OPAL Architect, IBM.
.
>
> Signed-off-by: Jordan Niethe
Yeah, this is a really good idea.
Reviewed-by: Stewart Smith
--
Stewart Smith
OPAL Architect, IBM.
e costly after this, (410ns->430ns on POWER9), but
> OPAL calls are generally not performance critical at this scale.
At least with this patch we can start to better measure things, and
that's a big plus. Also, When I get to start worrying about <1ms OPAL
calls, I think we can revisit optimising this path :)
--
Stewart Smith
OPAL Architect, IBM.
nd of wish it'd die rather than spread further.
Reviewed-by: Stewart Smith
--
Stewart Smith
OPAL Architect, IBM.
nitor hardware support registered
>
> Signed-off-by: Joel Stanley
Oh goodness yes.
Reviewed-by: Stewart Smith
--
Stewart Smith
OPAL Architect, IBM.
OOT_FULL_IPL, NULL);
> + else
> + rc = opal_cec_reboot();
> +
If the reboot type isn't supported, what should be the behvaiour? Reboot
the default way or don't reboot at all?
--
Stewart Smith
OPAL Architect, IBM.
r-groups");
> + if (!groups)
> + return ret;
Why not look for the compatible property?
--
Stewart Smith
OPAL Architect, IBM.
Michael Neuling writes:
> Signed-off-by: Michael Neuling
Acked-by: Stewart Smith
--
Stewart Smith
OPAL Architect, IBM.
Michael Neuling writes:
> +POWER9C DD1.2 and above are only avaliable with POWERNV and hence
PowerVM, not POWERNV
--
Stewart Smith
OPAL Architect, IBM.
Michael Neuling writes:
> Signed-off-by: Michael Neuling
> ---
> Documentation/powerpc/DAWR-POWER9.txt | 58 +++
> 1 file changed, 58 insertions(+)
> create mode 100644 Documentation/powerpc/DAWR-POWER9.txt
Acked-by: Stewart Smith
--
Stewart Smith
ixes: 78eaa10f027c ("cpuidle: powernv/pseries: Auto-promotion of snooze to
> deeper idle state")
> Cc: sta...@vger.kernel.org # v4.2+
Yes, it's a bug - we had a customer bug because we lacked this that
meant we had to do firmware changes rather than just tweaking what stop
states were used.
--
Stewart Smith
OPAL Architect, IBM.
Haren Myneni writes:
> On 06/03/2018 05:41 PM, Stewart Smith wrote:
>> Haren Myneni writes:
>>> On 06/01/2018 12:41 AM, Stewart Smith wrote:
>>>> Haren Myneni writes:
>>>>> NX increments readOffset by FIFO size in receive FIFO control register
>&g
Haren Myneni writes:
> On 06/01/2018 12:41 AM, Stewart Smith wrote:
>> Haren Myneni writes:
>>> NX increments readOffset by FIFO size in receive FIFO control register
>>> when CRB is read. But the index in RxFIFO has to match with the
>>> corresponding entry
chip_id, pid);
> + if (ret) {
> + pr_err("Failed to initialize NX coproc: %d\n", ret);
> + ret = opal_error_code(ret);
> + goto err_out;
> + }
> +
> coproc->ct = VAS_COP_TYPE_842_HIPRI;
I think this should be called for all priority queues as it would be at
least theoretically possible to only have Normal priority queues, in
which case this patch wouldn't fix the problem.
--
Stewart Smith
OPAL Architect, IBM.
;rmmod ; insmod" will crash, and possibly even issues over kexec?
--
Stewart Smith
OPAL Architect, IBM.
on is okay, as we have to keep compatibility with that firmware.
> --- a/include/linux/cpuidle.h
> +++ b/include/linux/cpuidle.h
> @@ -17,7 +17,7 @@
>
> #define CPUIDLE_STATE_MAX10
> #define CPUIDLE_NAME_LEN 16
> -#define CPUIDLE_DESC_LEN 32
> +#define CPUIDLE_DESC_LEN 60
Do we really get that long?
--
Stewart Smith
OPAL Architect, IBM.
Colin King <colin.k...@canonical.com> writes:
> From: Colin Ian King <colin.k...@canonical.com>
>
> Trivial fix to spelling mistake in hmi_error_types text
>
> Signed-off-by: Colin Ian King <colin.k...@canonical.com>
Reviewed-by: Stewart Smith <stew...@li
that one).
The idea behind that is that you can answer "where did all my CPUs go?"
by looking at the device tree rather than having to know the platform
specific way of how guards are stored.
--
Stewart Smith
OPAL Architect, IBM.
head to stable? It means that for single threaded
workloads, if you guard out a CPU core you'll not get WoF, which means
that performance goes down when you wouldn't expect it to. Right?
--
Stewart Smith
OPAL Architect, IBM.
ping them manually at the moment) and, I presume, anyone on
> this list is capable of sending no HTML email.
certainly one way to get those pesky IBM Verse users off. To be fair,
Documentation/process/email-clients.rst also warns them appropriately.
I fully support ditching HTML mail.
--
Stewart
Michael Ellerman <m...@ellerman.id.au> writes:
> Stewart Smith <stew...@linux.vnet.ibm.com> writes:
> ...
>>
>> Slightly stupid question: should we be disabling these here or should
>> Linux be better and deciding what states to use?
>>
>> I'm incl
few microseconds in case of stop0_lite. So snooze cannot still be
>> replaced by stop0_lite.
>
> I meant the other way around. Replace stop0_lite with snooze.
>
> So we would have snooze, stop0, stop2, and stop4 and/or 5.
Slightly stupid question: should we be disabling these here or should
Linux be better and deciding what states to use?
I'm inclined to say this is a Linux problem as it should make the
decision of what hardware feature to used based on the ones OPAL says
*can* be used.
I'm also open to be being convinced otherwise though...
--
Stewart Smith
OPAL Architect, IBM.
any(policy->cpus, set_pstate, _data, 1);
> + smp_call_function_any(policy->cpus, set_pstate, _data, 0);
> }
Should this have:
Fixes: eaa2c3aeef83f
and CC stable v4.7+ ?
--
Stewart Smith
OPAL Architect, IBM.
otherwise would have.
The "sane default" seems to be adequate for our purposes between
udbg_init_opal_common() and time_init() being called, and if it isn't,
then we should probably be setting it somewhere that isn't hvc_opal.c!
Signed-off-by: Stewart Smith <stew...@linux.ibm.com>
---
> arch/powerpc/platforms/powernv/opal-nvram.c | 2 ++
> 1 file changed, 2 insertions(+)
Acked-by: Stewart Smith <stew...@linux.ibm.com>
--
Stewart Smith
OPAL Architect, IBM.
ent to death :)
I reckon the panic() here is the right thing to do no matter
what.
Reviewed-by: Stewart Smith <stew...@linux.vnet.ibm.com>
--
Stewart Smith
OPAL Architect, IBM.
;
> Fixes : 1e1601b38e6e ("powerpc/powernv/idle: Restore SPRs for deep idle
> states via stop API.")
This should CC stable ?
We'll need this to enable stop11 in firmware and not break things, right?
--
Stewart Smith
OPAL Architect, IBM.
Michael Ellerman <m...@ellerman.id.au> writes:
> Brian King <brk...@linux.vnet.ibm.com> writes:
>> On 09/03/2017 06:19 PM, Stewart Smith wrote:
>>> Michael Ellerman <m...@ellerman.id.au> writes:
>>>>> 2. On a bare metal machine, if you set ipr.fa
to do that when they start working on
new API calls.
--
Stewart Smith
OPAL Architect, IBM.
irmware promise though, it's slightly less reliable than one
from a politician.
I'd say that in this case deferring to policy on what to do in event of
panic() is the right thing.
--
Stewart Smith
OPAL Architect, IBM.
n(-)
> create mode 100644 core/cpufeatures.c
> create mode 100644 doc/device-tree/ibm,powerpc-cpu-features/binding.txt
> create mode 100644
> doc/device-tree/ibm,powerpc-cpu-features/design.txt
Merged to master as of 7f4c8e8ce0b78ca046643d7f4f63d81f4fd11746 and has
made it into -rc4
--
Stewart Smith
OPAL Architect, IBM.
Alexandre Belloni <alexandre.bell...@bootlin.com> writes:
> On 02/08/2016 at 11:50:16 +1000, Stewart Smith wrote:
>> According to the OPAL docs:
>> https://github.com/open-power/skiboot/blob/skiboot-5.2.5/doc/opal-api/opal-rtc-read-3.txt
>> https://github.com/open-power
Benjamin Herrenschmidt <b...@kernel.crashing.org> writes:
> This message isn't terribly useful.
>
> Signed-off-by: Benjamin Herrenschmidt <b...@kernel.crashing.org>
Acked-by: Stewart Smith <stew...@linux.vnet.ibm.com>
> --- a/arch/powerpc/platforms/powernv/opal.c
generic sensors API?
>>
>
> Disabling/Enabling sensor groups is not supported in the current generic
> sensors
> API. And also we dont export all type of sensors in HWMON as not all of them
> are
> environment sensors (like performance).
Are there barriers to adding such concepts to the generic sensors API?
--
Stewart Smith
OPAL Architect, IBM.
Anju T Sudhakar <a...@linux.vnet.ibm.com> writes:
> On Wednesday 11 October 2017 01:55 AM, Stewart Smith wrote:
>> Michael Ellerman <m...@ellerman.id.au> writes:
>>> Anju T Sudhakar <a...@linux.vnet.ibm.com> writes:
>>>
>>>> Add a
ight thing and nothing special in
kernel. i.e. not to merge this.
--
Stewart Smith
OPAL Architect, IBM.
already have two ways of exposing sensors
to Linux: the OPAL_SENSOR API and the IMC API.
Why this method and not use the existing ones?
--
Stewart Smith
OPAL Architect, IBM.
th "memory-region" properties.
A more future-proof fix is likely possible, although more invasive and this
simple fix is perfectly suitable in the meantime while a more future-proof
fix is developed.
Signed-off-by: Stewart Smith <stew...@linux.vnet.ibm.com>
---
drivers/of/of_res
Rob Herring <r...@kernel.org> writes:
> On Thu, Sep 14, 2017 at 5:24 AM, Stewart Smith
> <stew...@linux.vnet.ibm.com> wrote:
>> There are two types of memory reservations firmware can ask the kernel
>> to make in the device tree: static and dynamic.
>> S
to do
(although I have not checked every real world device tree on the planet
for this condition)
Fixes: 3f0c8206644836e4f10a6b9fc47cda6a9a372f9b
Signed-off-by: Stewart Smith <stew...@linux.vnet.ibm.com>
---
NOTE: I've done only fairly limited testing of this on POWER, I
certainly haven't tested
prove.
>
> Yeah booting bare metal is where I see it (not using ipr.fast_reboot).
Hrm... We should probably enable that by default for petitboot then.
It'd at least cut some time off booting straight through to OS.
--
Stewart Smith
OPAL Architect, IBM.
e by anybody,
anywhere, ever.
> I think the majority of machines that have one of these adapters will be
> using it for their root disk, so I think the slow initialisation is just
> something we have to suffer.
It does seem that way currently.
--
Stewart Smith
OPAL Architect, IBM.
thing, you *could* go
and set a differnt powercap 180 times concurrently and we should do the
right thing in skiboot... but then you're sitting in skiboot rather than
sitting in linux being able to go run some other task on the thread.
--
Stewart Smith
OPAL Architect, IBM.
me says "you're overthinking this, get back
to the work you're meant to be doing" :)
--
Stewart Smith
OPAL Architect, IBM.
Michael Ellerman <m...@ellerman.id.au> writes:
> Stewart Smith <stew...@linux.vnet.ibm.com> writes:
>> Oliver O'Halloran <ooh...@gmail.com> writes:
>>> diff --git a/arch/powerpc/include/asm/opal-api.h
>>> b/arch/powerpc/include/asm/opal-api.
128
(another thought, along with the skiboot thoughts), I don't like the
SCRAPE_LOG name so much, as it's more of a "hey linux, here's some log
messages from firmware, possibly before you were
involved"... OPAL_FETCH_LOG ?
--
Stewart Smith
OPAL Architect, IBM.
on POWER9 to prevent this
> from causing a problem.
>
> Signed-off-by: Michael Neuling <mi...@neuling.org>
CC: stable?
--
Stewart Smith
OPAL Architect, IBM.
n, we'd have no way to detect that and we'd fail silently by
overwriting memory.
--
Stewart Smith
OPAL Architect, IBM.
if the class
exists but init is a no-op, then OPAL_IMC_COUNTERS_INIT should return
OPAL_SUCCESS and just do nothing. This future proofs everything, and the
API is that one *must* call _INIT before start.
--
Stewart Smith
OPAL Architect, IBM.
; + * "/reserved-memory" node.
> + */
> + for (dn = of_find_node_by_name(rm_node, "ibm,homer-image"); dn;
> + dn = of_find_node_by_name(dn, "ibm,homer-image")) {
> +
> + /* Get the chip id to which the above homer region belongs to */
> + if (of_property_read_u32(dn, "ibm,chip-id", _id))
> + goto err;
So, I was thinking on this (and should probably comment on the firmware
side as well).
I'd prefer an OPAL interface where instead of looking up where
ibm,homer-image is, we provide the kernel with a base address and then
have offsets into it.
That way, we don't tie the kernel code to counters that are only in the
HOMER region.
--
Stewart Smith
OPAL Architect, IBM.
on
boot.
We may hot plug/unplug CPUs, but we're not doing that from a hardware
level, what CPUs you get in the DT on PowerNV on boot is all you're
getting.
--
Stewart Smith
OPAL Architect, IBM.
ompatible node under the
top level ibm,opal-in-memory-counters node? (i'm not convinced that
having ibm,ibmc-counters-nest versus ibm,imc-counters-core and
ibm,imc-counters-thread as I see in the dts is correct though, as
they're all accessed exactly the same way?)
--
Stewart Smith
OPAL Architect, IBM.
+#include
> +
> +#define IMC_MAX_CHIPS32
> +#define IMC_MAX_PMUS 32
> +#define IMC_MAX_PMU_NAME_LEN 256
Why do we need a max length? We get the actual lengths from the device
tree, so we know at each point in time what the length of any new string
should be, right?
Otherwise you appear to be, in the general case, using 10x the memory
than you could.
--
Stewart Smith
OPAL Architect, IBM.
uot;);
> + if (!rm_node)
> + goto err;
> +
> + for_each_child_of_node(rm_node, child) {
> + if (of_property_read_string_index(child, "name", 0,
> + _name))
> + continue;
> +
, instead, I think firmware
should provide a 'ibm,vas' compatible node, rather than simply searching
through all the ibm,xscom nodes.
XSCOMs aren't something that Linux should really know about, it's a
debug interface, and one we use through PRD to do PRD-things, XSCOMs
aren't part of the architecture.
--
Stewart Smith
OPAL Architect, IBM.
Nicholas Piggin <npig...@gmail.com> writes:
> On Tue, 21 Mar 2017 15:42:22 +1100
> Stewart Smith <stew...@linux.vnet.ibm.com> wrote:
>
>> Nicholas Piggin <npig...@gmail.com> writes:
>> > With this patch and the Linux one, I can boot (in mambo) a POWER8
/hdata/cpu-common.c
> +++ b/hdata/cpu-common.c
> + { "vector-crypto",
> + CPU_ALL,
> + ISA_BASE, USABLE_HV|USABLE_OS|USABLE_PR,
> + HV_SUPPORT_NONE, OS_SUPPORT_NONE,
> + -1, -1, 38,
> + "vector", },
Did we want to break this down at all? Specifically maybe just the AES
instructions?
AFAIK it's been the only set where there was some amount of discussion
about somebody possibly not wanting to include.
--
Stewart Smith
OPAL Architect, IBM.
t:
> - pr_err("%s: unexpected OPAL error %d\n", __func__, rc);
> + pr_err("%s: Unexpected OPAL error %d\n", __func__, rc);
Do we need this?
--
Stewart Smith
OPAL Architect, IBM.
*bin_attr, char *to,
> + loff_t pos, size_t count)
> +{
> + if (!hdat_info.base)
> + return -ENODEV;
> +
> + return memory_read_from_buffer(to, count, , hdat_info.base,
> + hdat_info.size);
> +}
> +
Michael Ellerman <m...@ellerman.id.au> writes:
> Stewart Smith <stew...@linux.vnet.ibm.com> writes:
>
>> Vipin K Parashar <vi...@linux.vnet.ibm.com> writes:
>>> On Monday 13 February 2017 06:13 AM, Michael Ellerman wrote:
>>>> Vipin K Parashar
Rashmica Gupta <rashmic...@gmail.com> writes:
> +}
> +machine_device_initcall(powernv, memtrace_init);
> +
> +
> +
> +/* XXX FIXME DEBUG CRAP */
> +machine_device_initcall(pseries, memtrace_init);
Should the fixme be there?
--
Stewart Smith
OPAL Architect, IBM.
so if every CPU is being
>> scanned for errors, sleeping CPUs likely aren't the cause of failures.
>>
>> So, return OPAL_WRONG_STATE in xscom_read and xscom_write if the CPU is
>> sleeping.
>>
>> Signed-off-by: Russell Curre
end up missing some code, what about this instead:
Remove OPAL regex in powerpc to avoid false match
Signed-off-by: Stewart Smith <stew...@linux.vnet.ibm.com>
---
MAINTAINERS |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 39
-by: Vasant Hegde <hegdevas...@linux.vnet.ibm.com>
> ---
> arch/powerpc/platforms/powernv/opal-dump.c | 9 +++--
> 1 file changed, 3 insertions(+), 6 deletions(-)
Should also have:
Fixes: 8034f715f ("powernv/opal-dump: Convert to irq domain")
?
--
Stewart Smith
OPAL Architect, IBM.
-
> arch/powerpc/platforms/powernv/opal-dump.c | 9 ++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Acked-by: Stewart Smith <stew...@linux.vnet.ibm.com>
--
Stewart Smith
OPAL Architect, IBM.
s being
> scanned for errors, sleeping CPUs likely aren't the cause of failures.
>
> So, return OPAL_WRONG_STATE in xscom_read and xscom_write if the CPU is
> sleeping.
>
> Signed-off-by: Russell Currey <rus...@russell.cc>
> Reviewed-by: Ali
nabled by writing 1 to
> /sys/firmware/opal/force_full_ipl_reboot. On versions of skiboot that
> implement the OPAL_REBOOT_FULL_IPL reboot type, this will force an IPL. On
> versions that do not, print an error message on reboot and proceed with a
> regular reboot (which could be a
y POV this is basically a "my firmware is
> broken" workaround, so you're going to want to set it permanently until
> you update your firmware.
The only real world application I can see wanting to do that is perhaps
HTX - where it chooses what kind of bootme run it wants. So, well, for
certain definitions of "real world".
--
Stewart Smith
OPAL Architect, IBM.
special and set it
to DEFAULT_PSSCR_MASK in that case? That deals with old skiboot, new
kernel, and sets a pretty small special case that's easy to track into
the future as something we should watch out for.
Additionally, if we make skiboot set sane values in ~DEFAULT_PSSCR_MASK
for valid fields in PSSCR on boot/(also kexec?), then
we should end up in a situation where everything works with everything
(even if you don't get the best power saving). Specifically, new
skiboot, old kernel... but it looks like there's nothing currently
missing there
Should this patch also have Fixes: 3005c597ba4 and CC to stable?
--
Stewart Smith
OPAL Architect, IBM.
roneous flash nodes =).
>
> Quite :)
>
>> If we really just want to find compatible nodes anywhere, let's simplify i2c
>> and pdev_init into one function and make that behavior consistent with this
>> new patch.
>
> That seems OK to me.
>
> We should get an a
nged, 26 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/powerpc/opal/hotplug-aperture.txt
Forgive me for being absent on the whole discussion here, but is this an
OPAL specific binding? If so, shouldn't the docs also appear in the
skiboot tree?
--
Stewart Smith
OPAL Architect, IBM.
ntion that in commit message
here.
Also, should this go to stable?
--
Stewart Smith
OPAL Architect, IBM.
cold" to the BMC, the result of
that being that we'd get stuck in an infinite loop in opal_get_rtc_time.
We now retry a few times before returning the error higher up the stack.
Cc: sta...@vger.kernel.org
Signed-off-by: Stewart Smith <stew...@linux.vnet.ibm.com>
---
drivers/rtc
gt; not
> require an additional step of signing it, since the running kernel already
> trusts it.
- using current view of the hardware, flattened into a new dtb.
This should already be trusted, as it's what we're running now (boot +
runtime changes)
--
Stewart Smith
OPAL Architect, IBM.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
Ard Biesheuvel <ard.biesheu...@linaro.org> writes:
> On 13 July 2016 at 09:36, Russell King - ARM Linux
> <li...@armlinux.org.uk> wrote:
>> On Wed, Jul 13, 2016 at 02:59:51PM +1000, Stewart Smith wrote:
>>> Russell King - ARM Linux <li...@armlinux.org.uk> w
Russell King - ARM Linux <li...@armlinux.org.uk> writes:
> On Wed, Jul 13, 2016 at 02:59:51PM +1000, Stewart Smith wrote:
>> Russell King - ARM Linux <li...@armlinux.org.uk> writes:
>> > On Tue, Jul 12, 2016 at 10:58:05PM +0200, Petr Tesarik wrote:
>> >
er. Our bootloader is a
linux kernel and initramfs with a UI (petitboot) - this means we never
have to write a device driver twice: write a kernel one and you're done
(for booting from the device and using it in your OS).
--
Stewart Smith
OPAL Architect, IBM.
___
So, I assume that this license is compatible with the GPLv2?
https://people.gnome.org/~markmc/openssl-and-the-gpl.html has an
explanation and points to:
https://www.openssl.org/docs/faq.html#LEGAL2
which makes it anything but clearer.
it appear
uses the same console that
>> petitboot was configured to use (i.e., set the /chosen/linux,stdout-path
>> property). It also modifies the device tree to allow the kernel to inherit
>> Petitboot's Openfirmware framebuffer.
>
> Can some of this be done with the help of kern
an attack
vector? Is *every* command line option safe?
> In general, tampering with the hardware inventory of a machine opens up
> a security hole, and one must be very cautious which modifications are
> allowed. You're giving this power to an (unsigned, hence untrusted)
> userspace application; Eric argues that only the kernel should have
> this power.
In the case of petitboot on OpenPOWER, this (will) be a signed and
trusted kernel and userspace and verified by a previous bit of firmware.
--
Stewart Smith
OPAL Architect, IBM.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
ponding interfaces.
>
> Signed-off-by: Benjamin Herrenschmidt <b...@kernel.crashing.org>
These OPAL calls have the correct OPAL API numbers and they've been
assigned upstream in skiboot.
Acked-by: Stewart Smith <stew...@linux.vnet.ibm.com>
-
th a
dumb idea and a bug?
otherwise (including if above change is made)
Acked-by: Stewart Smith <stew...@linux.vnet.ibm.com>
--
Stewart Smith
OPAL Architect, IBM.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
hat only the "raw" type of
> OPAL console is supported, however machines that provide a hvsi console
> also provide a raw console so this is not an issue in practice.
>
> Actually-written-by: Benjamin Herrenschmidt <b...@kernel.crashing.org>
> Signed-off-by
ponding support to
> be merged into skiboot first, which was submitted here:
> http://patchwork.ozlabs.org/patch/625582/
Merged to skiboot as of 5477148a439fda9fb55ea4a828c958fcdcc10f2e - which
will make it into skiboot 5.3.x
--
Stewart Smith
OPAL Architect, IBM.
ld be skiboot 5.3.x or higher.
This could be something we start doing - there's enough random bits of
functionality we could tell the user exactly what they have to upgrade
to to have work.
--
Stewart Smith
OPAL Architect, IBM.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
mware. :)
It is. PAPR says we format NVRAM when it's corrupted. This is also true
for NVRAM for PowerNV (not just pseries guest).
--
Stewart Smith
OPAL Architect, IBM.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
-
>
> Required properties:
> -- comapatible: Should be "ibm,opal-rtc"
> +- compatible: Should be "ibm,opal-rtc"
>
> Optional properties:
> - wakeup-source: Decides if the wakeup is supported or not
Ac
here we're all
about OPAL.
With a slight change to the commit message,
Acked-by: Stewart Smith <stew...@linux.vnet.ibm.com>
--
Stewart Smith
OPAL Architect, IBM.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
herit in
hardware or software that this is computed from?
> +/* Interval after which the timer is queued to bring down global pstate */
> +#define GPSTATE_TIMER_INTERVAL 2000
in ms?
--
Stewart Smith
OPAL Architect, IBM.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
additional consoles
> to start properly.
>
> Signed-off-by: Samuel Mendoza-Jonas <s...@mendozajonas.com>
> Cc: <sta...@vger.kernel.org> # 4.1.x-
Tested on 4.4.6 - seemed to stop (some of) the problems I was having
when using it as a kernel for the bootloader on a FSP bas
1 - 100 of 250 matches
Mail list logo
