Breno Leitao writes:
> As discussed in the mailing list, renaming tm_disabled global variable
> since it has nothing to do with concept we have been using in
> tm_enable() and tm_enabled() functions. This will avoid a possible
> confusion that tm_enable() would change tm_disable variable.
>
> I a
Bjorn Helgaas writes:
> Please update the subject line from
>
> pci/iov: Expose VF drivers Auto Probe Globally
>
> to
>
> PCI/IOV: Add pci_vf_drivers_autoprobe() interface
...
>
>> + */
>> +void pci_vf_drivers_autoprobe(struct pci_dev *dev, bool auto_probe)
>> +{
>> +if (dev->is_physfn)
>>
> On Oct 20, 2017, at 9:57 AM, Khalid Aziz wrote:
>
> Patch 9/10
> When a processor supports additional metadata on memory pages, that
> additional metadata needs to be copied to new memory pages when those
> pages are moved. This patch allows architecture specific code to
> replace the defa
Hi Arnaldo,
Please pull an update to the JSON files for POWER9 PMU events.
The following changes since commit 148b43a3540bf25875bb5ab695a446950dc8d559:
tools headers: Synchronize kernel ABI headers wrt SPDX tags (2017-11-07
13:41:35 -0300)
are available in the git repository at:
https://g
Allow PowerPC to skip the full memory barrier in switch_mm(), and
only issue the barrier when scheduling into a task belonging to a
process that has registered to use expedited private.
Threads targeting the same VM but which belong to different thread
groups is a tricky case. It has a few consequ
The watchdog core includes a worker function which pings the
watchdog until user app starts pinging it and which also
pings it if the HW require more frequent pings.
Use that function instead of the dedicated timer.
In the mean time, we can allow the user to change the timeout.
Then change the tim
Abdul Haleem writes:
> Hi,
>
> Today's next kernel fails to boot on Power 7 Machine with below errors
> in boot log messages.
I am *not* seeing this on my Power7 machine (or any machine).
So this might be distro/toolchain specific?
cheers
Andy Shevchenko writes:
> On Tue, 2017-10-31 at 20:40 +0200, Andy Shevchenko wrote:
>> On Tue, 2017-10-31 at 13:33 -0500, Bjorn Helgaas wrote:
>> > On Tue, Oct 31, 2017 at 10:12 AM, Andy Shevchenko
>> > wrote:
>> > > On Fri, 2017-10-13 at 19:52 +0300, Andy Shevchenko wrote:
>> > > > ...which mak
As far as I can tell CONFIG_CPM is the right symbol to use to
conditionally compile the cpm-serial.c code.
Signed-off-by: Michael Ellerman
---
arch/powerpc/boot/Makefile | 3 ++-
arch/powerpc/boot/serial.c | 2 ++
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/boot/Ma
Only build the OPAL console code in when necessary. This looks like it
should use CONFIG_PPC_POWERNV, but because the opal-call.S code is
64-bit only, we must only build it when we're building the boot
wrapper 64-bit.
Signed-off-by: Michael Ellerman
---
arch/powerpc/boot/Makefile | 6 +++---
arc
The serial code in uartlite.c only matches if we find one of two
Xilinx (xlnx) nodes in the device tree, there's no need to build or
link the code on other platforms.
As far as I can tell CONFIG_XILINX_VIRTEX is the appropriate symbol to
use to conditionally compile the code.
Signed-off-by: Micha
On Wed, Nov 08, 2017 at 03:56:06PM +1100, Michael Ellerman wrote:
> "Aneesh Kumar K.V" writes:
>
> >>
> >> If it is decided to keep these kind of heuristics, can we get just a
> >> small but reasonably precise description of each change to the
> >> interface and ways for using the new functional
12 matches
Mail list logo
