On Tue, Dec 15, 2015 at 03:35:54AM +, Wang Nan wrote:
> Hi Naveen,
>
>Now I know your problem is in native building and the reason is
> missing proper $(ARCH). I think other than that there's another problem
> in libbpf's building: if your problem is unable to compile libbpf,
> feature che
This patch contains a problem.
On 2015/12/15 11:35, Wang Nan wrote:
From: "Naveen N. Rao"
perf build is currently (v4.4-rc5) broken on powerpc:
bpf.c:28:4: error: #error __NR_bpf not defined. libbpf does not support
your arch.
# error __NR_bpf not defined. libbpf does not support your arch
From: "Naveen N. Rao"
perf build is currently (v4.4-rc5) broken on powerpc:
bpf.c:28:4: error: #error __NR_bpf not defined. libbpf does not support
your arch.
# error __NR_bpf not defined. libbpf does not support your arch.
^
Fix this by including tools/scripts/Makefile.arch for the prope
On 15/12/2015 at 18:09:14 +1100, Daniel Axtens wrote :
> GregorianDay() is supposed to calculate the day of the week
> (tm->tm_wday) for a given day/month/year. In that calcuation it
> indexed into an array called MonthOffset using tm->tm_mon-1. However
> tm_mon is zero-based, not one-based, so thi
Stephen Rothwell writes:
> Hi Andrew,
>
> Today's linux-next merge of the akpm-current tree got conflicts in:
>
> arch/powerpc/include/asm/nohash/64/pgtable.h
> arch/powerpc/mm/pgtable_64.c
>
> between various commits from the powerpc tree and commits:
>
> e56ebae0dd4c ("powerpc, thp: remov
On Fri, 2015-20-11 at 04:15:32 UTC, Michael Neuling wrote:
> Print MSR TM bits in oops messages. This appends them to the end
> like this:
>
> MSR: 800502823031
>
> You get the TM[] only if at least one TM MSR bit is set. Inside the
> TM[], E means Enabled (bit 32), S means Suspended (
On Tue, 2015-24-11 at 02:05:38 UTC, Michael Ellerman wrote:
> This doesn't really belong in harness.c, it's a helper function. So move
> it into utils.c.
>
> Signed-off-by: Michael Ellerman
Applied to powerpc next.
https://git.kernel.org/powerpc/c/fcb45ec074725baeb3aaa1b1
cheers
__
On Fri, 2015-20-11 at 04:15:33 UTC, Michael Neuling wrote:
> Test the kernel's signal return code to ensure that it doesn't crash
> when both the transactional and suspend MSR bits are set in the signal
> context.
>
> Signed-off-by: Michael Neuling
> Tested-by: Anshuman Khandual
Applied to powe
On Tue, 2015-24-11 at 02:05:39 UTC, Michael Ellerman wrote:
> We already do this twice and want to add another so add a helper.
>
> Signed-off-by: Michael Ellerman
Applied to powerpc next.
https://git.kernel.org/powerpc/c/ede8ef3f824ea6e853a5e4b2
cheers
On Fri, 2015-20-11 at 04:15:34 UTC, Michael Neuling wrote:
> Test the kernels signal generation code to ensure it can handle an
> invalid stack pointer when transactional.
>
> Signed-off-by: Michael Neuling
> Tested-by: Anshuman Khandual
Applied to powerpc next, thanks.
https://git.kernel.org/
On Tue, 2015-24-11 at 02:05:40 UTC, Michael Ellerman wrote:
> Move have_htm_nosc() into a new tm.h, and add a new helper, have_htm()
> which we'll use in the next patch.
>
> Signed-off-by: Michael Ellerman
Applied to powerpc next.
https://git.kernel.org/powerpc/c/34dc8b279dc5dd3ce8632980
cheer
On Tue, 2015-01-12 at 11:13:42 UTC, Vipin K Parashar wrote:
> Kernel prints respective warnings about various EPOW events for
> user information/action after parsing EPOW interrupts. At times
> below EPOW reset event warning is seen to be flooding kernel log
> over a period of time.
>
> May 25 03:
On Mon, 2015-02-11 at 01:30:32 UTC, Boqun Feng wrote:
> According to memory-barriers.txt, xchg*, cmpxchg* and their atomic_
> versions all need to be fully ordered, however they are now just
> RELEASE+ACQUIRE, which are not fully ordered.
>
> So also replace PPC_RELEASE_BARRIER and PPC_ACQUIRE_BAR
On Mon, 2015-02-11 at 01:30:31 UTC, Boqun Feng wrote:
> According to memory-barriers.txt:
>
> > Any atomic operation that modifies some state in memory and returns
> > information about the state (old or new) implies an SMP-conditional
> > general memory barrier (smp_mb()) on each side of the actu
On Wed, 2015-25-11 at 02:46:25 UTC, Rashmica Gupta wrote:
> Currently if you are in xmon without an oops etc. to view the kernel
> version you have to type "d $linux_banner" - not necessarily obvious. As
> this is useful information, append to the output of "e" command.
>
> Example output:
> $mon>
On Tue, 2015-01-12 at 03:51:38 UTC, Rashmica Gupta wrote:
> All users of QPACE have upgraded to QPACE2 so remove the Cell QPACE code.
>
> Signed-off-by: Rashmica Gupta
> Acked-by: Arnd Bergmann
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/24ad1648edcc8b1c4a68c406
cheers
_
On Tue, 2015-08-12 at 22:09:20 UTC, Rashmica Gupta wrote:
> When a transaction is aborted, VSR values should rollback to the
> checkpointed values before the transaction began. VSRs used elsewhere in
> the kernel during a transaction, or while the transaction is suspended
> should not affect the ch
On 2015/12/15 03:35AM, Wang Nan wrote:
> Hi Naveen,
>
>Now I know your problem is in native building and the reason is
> missing proper $(ARCH). I think other than that there's another problem
> in libbpf's building: if your problem is unable to compile libbpf,
> feature checker should find it
On 2015/12/15 08:51AM, Wang Nan wrote:
> From: "Naveen N. Rao"
>
> perf build is currently (v4.4-rc5) broken on powerpc:
>
> bpf.c:28:4: error: #error __NR_bpf not defined. libbpf does not support
> your arch.
> # error __NR_bpf not defined. libbpf does not support your arch.
> ^
>
> Fix
Hello Andy,
Thank you for your feedback. Some inline answers.
Regards,
Igal Liberman
> -Original Message-
> From: Andy Fleming [mailto:aflem...@gmail.com]
> Sent: Tuesday, December 08, 2015 10:18 PM
> To: Liberman Igal-B31950
> Cc: net...@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; l
Hi all,
This is v6 of the series.
Link for v1: https://lkml.org/lkml/2015/8/27/798
Link for v2: https://lkml.org/lkml/2015/9/16/527
Link for v3: https://lkml.org/lkml/2015/10/12/368
Link for v4: https://lkml.org/lkml/2015/10/14/670
Link for v5: https://lkml.org/lkml/2015/10/26/141
Changes since
Some architectures may have their special barriers for acquire, release
and fence semantics, so that general memory barriers(smp_mb__*_atomic())
in the default __atomic_op_*() may be too strong, so allow architectures
to define their own helpers which can overwrite the default helpers.
Signed-off-
On powerpc, acquire and release semantics can be achieved with
lightweight barriers("lwsync" and "ctrl+isync"), which can be used to
implement __atomic_op_{acquire,release}.
For release semantics, since we only need to ensure all memory accesses
that issue before must take effects before the -stor
Implement xchg{,64}_relaxed and atomic{,64}_xchg_relaxed, based on these
_relaxed variants, release/acquire variants and fully ordered versions
can be built.
Note that xchg{,64}_relaxed and atomic_{,64}_xchg_relaxed are not
compiler barriers.
Signed-off-by: Boqun Feng
---
arch/powerpc/include/a
Implement cmpxchg{,64}_relaxed and atomic{,64}_cmpxchg_relaxed, based on
which _release variants can be built.
To avoid superfluous barriers in _acquire variants, we implement these
operations with assembly code rather use __atomic_op_acquire() to build
them automatically.
For the same reason, we
On Fri 2015-12-11 15:30:54, Andrew Morton wrote:
> On Fri, 11 Dec 2015 23:21:13 + Russell King - ARM Linux
> wrote:
>
> > On Fri, Dec 11, 2015 at 02:57:25PM -0800, Andrew Morton wrote:
> > > This is a bit messy. NEED_PRINTK_NMI is an added-on hack for one
> > > particular arm variant. From
On 12/14/2015 3:06 PM, Uma Krishnan wrote:
Having a date for the driver requires it to be updated quite
often. Removing the date which is not necessary. Also made
use of the existing symbol to print the driver name.
Signed-off-by: Uma Krishnan
---
Acked-by: Manoj N. Kumar
__
[[PATCH 0/5] drivers/tty: make more bool drivers explicitly non-modular] On
18/10/2015 (Sun 18:21) Paul Gortmaker wrote:
> This next set of patches to drivers/tty fixes up more drivers that would
> perhaps appear modular when looking at the code, but are controlled by
> a bool Kconfig. We make s
Just testing that things are behaving the way they should. Uses more
threads than cpus to see if the following values persist with context
switching:
- the FS (failure summary) flag in TEXASR
- TFIAR and TFHAR
Signed-off-by: Rashmica Gupta
---
tools/testing/selftests/powerpc/tm/.gitignore | 1
From: Zhang Zhuoyu
Remove paradoxical and unnecessary lines before disable local interrupt.
Signed-off-by: Zhang Zhuoyu
---
arch/powerpc/kernel/irq.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/powerpc/kernel/irq.c b/arch/powerpc/kernel/irq.c
index 290559d..03fa686 100644
--- a/a
This patch modifies KVM to cause a guest exit with
KVM_EXIT_NMI instead of immediately delivering a 0x200
interrupt to guest upon machine check exception in
guest address. Exiting the guest enables QEMU to build
error log and deliver machine check exception to guest
OS (either via guest OS register
Hi,
A couple of things.
Firstly, your two email addresses don't match:
Zhang Zhuoyu writes:
> From: Zhang Zhuoyu
These lines do seem odd! Are they causing a problem?
I'd be more comfortable removing them if I understood why they were
added. But they've been around since the beginning of git
Hi,
> This patch also introduces a new KVM capability to
> control how KVM behaves on machine check exception.
> Without this capability, KVM redirects machine check
> exceptions to guest's 0x200 vector if the address in
> error belongs to guest. With this capability KVM
> causes a guest exit wit
33 matches
Mail list logo
