Re: powerpc: Sort the selects under CONFIG_PPC

On Mon, 2017-03-06 at 12:05:17 UTC, Michael Ellerman wrote: > We have a big list of selects under CONFIG_PPC, and currently they're > completely unsorted. This means people tend to add new selects at the > bottom of the list, and so two commits which both add a new select will > often conflict. >

Re: powerpc/64: Fix L1D cache shape vector reporting L1I values

On Mon, 2017-03-06 at 11:15:29 UTC, Michael Ellerman wrote: > It seems we didn't pay quite enough attention when testing the new cache > shape vectors, which means we didn't notice the bug where the vector for > the L1D was using the L1I values. Fix it, resulting in eg: > > L1I cache size:

Re: powerpc: Avoid panic during boot due to divide by zero in init_cache_info()

On Sat, 2017-03-04 at 23:54:34 UTC, Anton Blanchard wrote: > From: Anton Blanchard > > I see a panic in early boot when building with a recent gcc toolchain. > The issue is a divide by zero, which is undefined. Older toolchains > let us get away with it: > > int foo(int a) {

Re: [v2] powerpc/xics,icp-opal: Fix CPPR setting for icp-opal

On Fri, 2017-03-03 at 00:58:44 UTC, Balbir Singh wrote: > CPPR (Current Processor Priority Register) emulation on icp-opal > uses a single priority in the backend and that can cause CPU > hotplug to be affected when we try to send an IPI to it. > > The fix is in migrate_irqs_away, the fix does

Re: [kernel] powerpc/powernv: Fix clobbered MSR

On Thu, 2017-03-02 at 06:41:24 UTC, Alexey Kardashevskiy wrote: > If CONFIG_DEBUG_INFO_SPLIT is not set but CONFIG_DEBUG_INFO is, > the kernel makefile just adds "-g" and the scripts/gcc-goto.sh test for > the "asm goto ("" entry)" support succedes and adds > -DCC_HAVE_ASM_GOTO to

Re: [V3,1/2] powerpc: Parse the command line before calling CAS

On Tue, 2017-02-28 at 06:03:47 UTC, Suraj Jitindar Singh wrote: > On POWER9 the hypervisor requires the guest to decide whether it would > like to use a hash or radix mmu model at the time it calls > ibm,client-architecture-support (CAS) based on what the hypervisor has > said it's allowed to do.

Re: [v2] powernv:idle: Fix bug due to labeling ambiguity in power_enter_stop

On Mon, 2017-02-27 at 05:40:07 UTC, "Gautham R. Shenoy" wrote: > From: "Gautham R. Shenoy" > > Commit 09206b600c76 ("powernv: Pass PSSCR value and mask to > power9_idle_stop") added additional code in power_enter_stop() to > distinguish between stop requests whose PSSCR

Re: powerpc/64: Invalidate process table caching after setting process table

On Mon, 2017-02-27 at 03:32:41 UTC, Paul Mackerras wrote: > The POWER9 MMU reads and caches entries from the process table. > When we kexec from one kernel to another, the second kernel sets > its process table pointer but doesn't currently do anything to > make the CPU invalidate any cached

Re: [RESEND] selftest/powerpc/alignment: Fix false failures for skipped tests

On Sun, 2017-02-26 at 06:08:39 UTC, Sachin Sant wrote: > Tests under alignment subdirectory are skipped when executed on previous > generation hardware, but harness still marks them as failed. > > test: test_copy_unaligned > tags: git_version:unknown > [SKIP] Test skipped on line 26 > skip:

Re: powerpc: booke: fix boot crash due to null hugepd

On Thu, 2017-02-16 at 15:11:29 UTC, laurentiu.tu...@nxp.com wrote: > From: Laurentiu Tudor > > On 32-bit book-e machines, hugepd_ok() does not take > into account null hugepd values, causing this crash at boot: > > Unable to handle kernel paging request for data at

Re: [v3, 1/2] powerpc: Emulation support for load/store instructions on LE

On Tue, 2017-02-14 at 09:16:42 UTC, Ravi Bangoria wrote: > emulate_step() uses a number of underlying kernel functions that were > initially not enabled for LE. This has been rectified since. So, fix > emulate_step() for LE for the corresponding instructions. > > Reported-by: Anton Blanchard

Re: powerpc/64: Fix checksum folding in csum_add

On Sat, 2017-02-04 at 09:03:40 UTC, Shile Zhang wrote: > fix the missed point in Paul's patch: > "powerpc/64: Fix checksum folding in csum_tcpudp_nofold and > ip_fast_csum_nofold" > > Signed-off-by: Shile Zhang > Acked-by: Paul Mackerras Applied to

Re: [2/3] powerpc: allow compilation on cross-endian toolchain

On Sun, 2016-11-27 at 02:46:20 UTC, Nicholas Piggin wrote: > Subject: [PATCH] powerpc: allow compilation on cross-endian toolchain > > GCC can compile with either endian, but the ABI version always > defaults to the default endian. Alan Modra says: > > you need both -mbig and -mabi=elfv1 to

Re: [PATCH v5 05/15] livepatch/powerpc: add TIF_PATCH_PENDING thread flag

Josh Poimboeuf writes: > Add the TIF_PATCH_PENDING thread flag to enable the new livepatch > per-task consistency model for powerpc. The bit getting set indicates > the thread has a pending patch which needs to be applied when the thread > exits the kernel. > > The bit is

[PATCH kernel v7 03/10] powerpc/iommu/vfio_spapr_tce: Cleanup iommu_table disposal

At the moment iommu_table can be disposed by either calling iommu_table_free() directly or it_ops::free(); the only implementation of free() is in IODA2 - pnv_ioda2_table_free() - and it calls iommu_table_free() anyway. As we are going to have reference counting on tables, we need an unified way

[PATCH kernel v7 02/10] powerpc/powernv/iommu: Add real mode version of iommu_table_ops::exchange()

In real mode, TCE tables are invalidated using special cache-inhibited store instructions which are not available in virtual mode This defines and implements exchange_rm() callback. This does not define set_rm/clear_rm/flush_rm callbacks as there is no user for those - exchange/exchange_rm are

[PATCH kernel v7 00/10] powerpc/kvm/vfio: Enable in-kernel acceleration

This is my current queue of patches to add acceleration of TCE updates in KVM. This is based on Linus'es tree sha1 c1ae3cfa0e89 v4.11-rc1. Please comment. Thanks. Changes: v7: * added realmode's WARN_ON_ONCE_RM in arch/powerpc/kvm/book3s_64_vio_hv.c v6: * reworked the last patch in terms of

[PATCH kernel v7 10/10] KVM: PPC: VFIO: Add in-kernel acceleration for VFIO

This allows the host kernel to handle H_PUT_TCE, H_PUT_TCE_INDIRECT and H_STUFF_TCE requests targeted an IOMMU TCE table used for VFIO without passing them to user space which saves time on switching to user space and back. This adds H_PUT_TCE/H_PUT_TCE_INDIRECT/H_STUFF_TCE handlers to KVM. KVM

[PATCH kernel v7 09/10] KVM: PPC: iommu: Unify TCE checking

This reworks helpers for checking TCE update parameters in way they can be used in KVM. This should cause no behavioral change. Signed-off-by: Alexey Kardashevskiy --- Changes: v6: * s/tce/gpa/ as TCE without permission bits is a GPA and this is what is passed everywhere ---

[PATCH kernel v7 08/10] KVM: PPC: Use preregistered memory API to access TCE list

VFIO on sPAPR already implements guest memory pre-registration when the entire guest RAM gets pinned. This can be used to translate the physical address of a guest page containing the TCE list from H_PUT_TCE_INDIRECT. This makes use of the pre-registrered memory API to access TCE list pages in

[PATCH kernel v7 07/10] KVM: PPC: Pass kvm* to kvmppc_find_table()

The guest view TCE tables are per KVM anyway (not per VCPU) so pass kvm* there. This will be used in the following patches where we will be attaching VFIO containers to LIOBNs via ioctl() to KVM (rather than to VCPU). Signed-off-by: Alexey Kardashevskiy Reviewed-by: David Gibson

[PATCH kernel v7 06/10] KVM: PPC: Enable IOMMU_API for KVM_BOOK3S_64 permanently

It does not make much sense to have KVM in book3s-64 and not to have IOMMU bits for PCI pass through support as it costs little and allows VFIO to function on book3s KVM. Having IOMMU_API always enabled makes it unnecessary to have a lot of "#ifdef IOMMU_API" in arch/powerpc/kvm/book3s_64_vio*.

[PATCH kernel v7 05/10] KVM: PPC: Reserve KVM_CAP_SPAPR_TCE_VFIO capability number

This adds a capability number for in-kernel support for VFIO on SPAPR platform. The capability will tell the user space whether in-kernel handlers of H_PUT_TCE can handle VFIO-targeted requests or not. If not, the user space must not attempt allocating a TCE table in the host kernel via the

[PATCH kernel v7 04/10] powerpc/vfio_spapr_tce: Add reference counting to iommu_table

So far iommu_table obejcts were only used in virtual mode and had a single owner. We are going to change this by implementing in-kernel acceleration of DMA mapping requests. The proposed acceleration will handle requests in real mode and KVM will keep references to tables. This adds a kref to

[PATCH kernel v7 01/10] powerpc/mmu: Add real mode support for IOMMU preregistered memory

This makes mm_iommu_lookup() able to work in realmode by replacing list_for_each_entry_rcu() (which can do debug stuff which can fail in real mode) with list_for_each_entry_lockless(). This adds realmode version of mm_iommu_ua_to_hpa() which adds explicit vmalloc'd-to-linear address conversion.

Re: [RESEND PATCH] powerpc/pseries: move struct hcall_stats to c file

"Tobin C. Harding" writes: > struct hcall_stats is only used in hvCall_inst.c. > > Move struct hcall_stats to hvCall_inst.c > > Resolves: #54 > Signed-off-by: Tobin C. Harding > --- > > Is this correct, adding 'Resolves: #XX' when fixing > github.com/linuxppc/linux

linux-next: manual merge of the rcu tree with the powerpc-fixes tree

Hi Paul, Today's linux-next merge of the rcu tree got a conflict in: arch/powerpc/Kconfig between commit: a7d2475af7ae ("powerpc: Sort the selects under CONFIG_PPC") from the powerpc-fixes tree and commit: 9252dd3a96a7 ("rcu: Make arch select smp_mb__after_unlock_lock() strength")

[PATCH] powerpc/boot: Fix zImage TOC alignment

Recent toolchains force the TOC to be 256 byte aligned. We need to enforce this alignment in the zImage linker script, otherwise pointers to our TOC variables (__toc_start) could be incorrect. If the actual start of the TOC and __toc_start don't have the same value we crash early in the zImage

Re: open list?

Hi Tobin, On Wed, 8 Mar 2017 08:00:29 +1100 "Tobin C. Harding" wrote: > > On Tue, Mar 07, 2017 at 01:16:34PM +0100, Christophe LEROY wrote: > > > > > > Le 07/03/2017 à 11:02, Tobin C. Harding a écrit : > > >scripts/get_maintainers.pl says this is an open list; > > > > >

Re: open list?

On Tue, Mar 07, 2017 at 01:16:34PM +0100, Christophe LEROY wrote: > > > Le 07/03/2017 à 11:02, Tobin C. Harding a écrit : > >scripts/get_maintainers.pl says this is an open list; > > > >linuxppc-dev@lists.ozlabs.org (open list:LINUX FOR POWERPC (32-BIT AND > >64-BIT)) > > > >Patches I've sent

Re: [PowerPC] XFS : Metadata corruption detected at 0x60000000382100b0, xfs_agf block

On 3/3/17 3:04 AM, Abdul Haleem wrote: > Hi, > > Reboot fails for PowerPC machine running RHEL7.3 (3.10.0-514.el7) > following these messages: Generally it's best to report RHEL bugs to Red Hat. > SGI XFS with ACLs, security attributes, no debug enabled > XFS (dm-0): Mounting V5 Filesystem >

Re: [next 20170227] CPU remove DLPAR operation WARN @ lib/refcount.c:128

This is likely a legitimate bug: something took the kref object negative. (Which was noticed due to the recent migration of kref from atomic_t to refcount_t which will refuse to perform dangerous refcounting actions.) If I had to guess, I think it's dlpar_cpu_exists(), which is calling

Re: [PATCH 06/18] pstore: Extract common arguments into structure

On Tue, Mar 7, 2017 at 6:55 AM, Kees Cook wrote: > The read/mkfile pair pass the same arguments and should be cleared > between calls. Move to a structure and wipe it after every loop. > > Signed-off-by: Kees Cook > --- > fs/pstore/platform.c | 55

Re: [PATCH 03/18] pstore: Avoid race in module unloading

Hi Kees, On Tue, Mar 7, 2017 at 6:55 AM, Kees Cook wrote: > Technically, it might be possible for struct pstore_info to go out of > scope after the module_put(), so report the backend name first. But in that case, using pstore will crash the kernel anyway, right? If so,

Re: [RESEND PATCH 1/6] trace/kprobes: fix check for kretprobe offset within function entry

Please start a new thread. When sending patches as replies to other patch threads, especially this deep into the thread, they will most likely get ignored. -- Steve

Re: [PATCH v4 1/3] perf: probe: factor out the ftrace README scanning

FYI, When creating new patch series, please start a new thread, and don't post a patch as a reply to another patch. It gets easily lost that way. -- Steve On Thu, 2 Mar 2017 23:25:05 +0530 "Naveen N. Rao" wrote: > Simplify and separate out the ftrace README

[PATCH] powerpc: kprobes: convert __kprobes to NOKPROBE_SYMBOL()

Along similar lines as commit 9326638cbee2 ("kprobes, x86: Use NOKPROBE_SYMBOL() instead of __kprobes annotation"), convert __kprobes annotation to either NOKPROBE_SYMBOL() or nokprobe_inline. The latter forces inlining, in which case the caller needs to be added to NOKPROBE_SYMBOL(). Also: -

Re: [PATCH] net: toshiba: ps3_genic_net: use new api ethtool_{get|set}_link_ksettings

On 03/05/2017 02:21 PM, Philippe Reynes wrote: The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. As I don't have the hardware, I'd be very pleased if someone may test this patch. I tested this applied to v4.11-rc1 and it seems to work

Re: [PATCH 06/18] pstore: Extract common arguments into structure

On Tue, Mar 7, 2017 at 8:22 AM, Namhyung Kim wrote: > On Tue, Mar 7, 2017 at 6:55 AM, Kees Cook wrote: >> The read/mkfile pair pass the same arguments and should be cleared >> between calls. Move to a structure and wipe it after every loop. >> >>

[PATCH v2 6/6] perf: powerpc: choose local entry point with kretprobes

perf now uses an offset from _text/_stext for kretprobes if the kernel supports it, rather than the actual function name. As such, let's choose the LEP for powerpc ABIv2 so as to ensure the probe gets hit. Do it only if the kernel supports specifying offsets with kretprobes. Signed-off-by: Naveen

Re: [PATCH 5/6] perf: probes: move ftrace README parsing logic into trace-event-parse.c

On 2017/03/07 04:51PM, Masami Hiramatsu wrote: > On Tue, 7 Mar 2017 16:17:40 +0530 > "Naveen N. Rao" wrote: > > > probe-file.c needs libelf, but scanning ftrace README does not require > > that. As such, move the ftrace README scanning logic out of probe-file.c

4.11.0-rc1 boot resulted in WARNING: CPU: 14 PID: 1722 at fs/sysfs/dir.c:31 .sysfs_warn_dup+0x78/0xb0

Hi, Today's mainline (4.11.0-rc1) booted with warnings on Power7 LPAR. Issue is not reproducible all the time. traces: Found device VDASD 5. Mounting /home... Reached target Swap. Found device VDASD 2. Mounting /boot... sysfs: cannot create duplicate filename '/fs/xfs/sda'

Re: [PATCH 03/18] pstore: Avoid race in module unloading

On Tue, Mar 7, 2017 at 8:16 AM, Namhyung Kim wrote: > Hi Kees, > > On Tue, Mar 7, 2017 at 6:55 AM, Kees Cook wrote: >> Technically, it might be possible for struct pstore_info to go out of >> scope after the module_put(), so report the backend name

Re: [PATCH v5 01/15] stacktrace/x86: add function for detecting reliable stack traces

On Tue, Mar 07, 2017 at 05:50:55PM +1100, Balbir Singh wrote: > On Mon, 2017-02-13 at 19:42 -0600, Josh Poimboeuf wrote: > > For live patching and possibly other use cases, a stack trace is only > > useful if it can be assured that it's completely reliable. Add a new > >

Re: [PATCH 5/6] perf: probes: move ftrace README parsing logic into trace-event-parse.c

On Tue, 7 Mar 2017 16:17:40 +0530 "Naveen N. Rao" wrote: > probe-file.c needs libelf, but scanning ftrace README does not require > that. As such, move the ftrace README scanning logic out of probe-file.c > and into trace-event-parse.c. As far as I can see,

Re: [PATCH v5.1 15/15] livepatch: allow removal of a disabled patch

On Mon, 6 Mar 2017, Josh Poimboeuf wrote: > > Currently we do not allow patch module to unload since there is no > method to determine if a task is still running in the patched code. > > The consistency model gives us the way because when the unpatching > finishes we know that all tasks were

Re: [PATCH 5/6] perf: probes: move ftrace README parsing logic into trace-event-parse.c

On 2017/03/07 03:03PM, Masami Hiramatsu wrote: > On Tue, 7 Mar 2017 16:17:40 +0530 > "Naveen N. Rao" wrote: > > > probe-file.c needs libelf, but scanning ftrace README does not require > > that. As such, move the ftrace README scanning logic out of probe-file.c

Re: [PATCH v5 13/15] livepatch: change to a per-task consistency model

On Mon, 13 Feb 2017, Josh Poimboeuf wrote: > Change livepatch to use a basic per-task consistency model. This is the > foundation which will eventually enable us to patch those ~10% of > security patches which change function or data semantics. This is the > biggest remaining piece needed to

Re: [PATCH 5/6] perf: probes: move ftrace README parsing logic into trace-event-parse.c

On Tue, 7 Mar 2017 16:17:40 +0530 "Naveen N. Rao" wrote: > probe-file.c needs libelf, but scanning ftrace README does not require > that. As such, move the ftrace README scanning logic out of probe-file.c > and into trace-event-parse.c. Hmm, it seems

Re: [PATCH kernel v6 10/10] KVM: PPC: VFIO: Add in-kernel acceleration for VFIO

On Tue, Mar 07, 2017 at 10:07:27PM +1100, Alexey Kardashevskiy wrote: > On 06/03/17 16:04, Alexey Kardashevskiy wrote: > > On 06/03/17 15:30, David Gibson wrote: > >> On Fri, Mar 03, 2017 at 06:09:25PM +1100, Alexey Kardashevskiy wrote: > >>> On 03/03/17 16:59, David Gibson wrote: > On Thu,

[GIT PULL] Please pull powerpc/linux.git powerpc-4.11-3 tag

Hi Linus, Please pull the first set of powerpc fixes for 4.11: The following changes since commit b286cedd473006b33d5ae076afac509e6b2c3bf4: Merge tag 'powerpc-4.11-2' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux (2017-03-01 10:10:16 -0800) are available in the git

Re: open list?

Le 07/03/2017 à 11:02, Tobin C. Harding a écrit : scripts/get_maintainers.pl says this is an open list; linuxppc-dev@lists.ozlabs.org (open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)) Patches I've sent with this list cc'd have not been getting through. I resent one to check if it was a user

[PATCH][Linux] powerpc/64s: cpufeatures: add initial implementation for cpufeatures

The /cpus/features dt binding describes architected CPU features along with some compatibility, privilege, and enablement properties that allow flexibility with discovering and enabling capabilities. Presence of this feature implies a base level of functionality, then additional feature nodes

[PATCH][OPAL] cpufeatures: add base and POWER8, POWER9 /cpus/features dt

With this patch and the Linux one, I can boot (in mambo) a POWER8 or POWER9 without looking up any cpu tables, and mainly looking at PVR for MCE and PMU. Machine and ISA speicfic features that are not abstracted by firmware and not captured here will have to be handled on a case by case basis,

[PATCH 0/2 v2] cpufeatures compatibility for OPAL and Linux

Hi, This is a bit more complete implementation that also works on POWER9. Any comments would be welcome. Thanks, Nick

Re: [PATCH kernel v6 10/10] KVM: PPC: VFIO: Add in-kernel acceleration for VFIO

On 06/03/17 16:04, Alexey Kardashevskiy wrote: > On 06/03/17 15:30, David Gibson wrote: >> On Fri, Mar 03, 2017 at 06:09:25PM +1100, Alexey Kardashevskiy wrote: >>> On 03/03/17 16:59, David Gibson wrote: On Thu, Mar 02, 2017 at 07:56:44PM +1100, Alexey Kardashevskiy wrote: > This allows

[RESEND PATCH 1/6] trace/kprobes: fix check for kretprobe offset within function entry

perf specifies an offset from _text and since this offset is fed directly into the arch-specific helper, kprobes tracer rejects installation of kretprobes through perf. Fix this by looking up the actual offset from a function for the specified sym+offset. Refactor and reuse existing routines to

[RESEND PATCH 3/6] perf: probe: factor out the ftrace README scanning

Simplify and separate out the ftrace README scanning logic into a separate helper. This is used subsequently to scan for all patterns of interest and to cache the result. Since we are only interested in availability of probe argument type x, we will only scan for that. Acked-by: Masami Hiramatsu

[RESEND PATCH 2/6] powerpc: kretprobes: override default function entry offset

With ABIv2, we offset 8 bytes into a function to get at the local entry point. Acked-by: Ananth N Mavinakayanahalli Acked-by: Michael Ellerman Signed-off-by: Naveen N. Rao --- arch/powerpc/kernel/kprobes.c | 9

[PATCH 5/6] perf: probes: move ftrace README parsing logic into trace-event-parse.c

probe-file.c needs libelf, but scanning ftrace README does not require that. As such, move the ftrace README scanning logic out of probe-file.c and into trace-event-parse.c. Signed-off-by: Naveen N. Rao --- tools/perf/util/probe-file.c| 87

[RESEND PATCH 6/6] perf: powerpc: choose local entry point with kretprobes

perf now uses an offset from _text/_stext for kretprobes if the kernel supports it, rather than the actual function name. As such, let's choose the LEP for powerpc ABIv2 so as to ensure the probe gets hit. Do it only if the kernel supports specifying offsets with kretprobes. Acked-by: Masami

[RESEND PATCH 4/6] perf: kretprobes: offset from reloc_sym if kernel supports it

We indicate support for accepting sym+offset with kretprobes through a line in ftrace README. Parse the same to identify support and choose the appropriate format for kprobe_events. As an example, without this perf patch, but with the ftrace changes: naveen@ubuntu:~/linux/tools/perf$ sudo cat

Re: [PATCH v4 2/3] perf: kretprobes: offset from reloc_sym if kernel

On 2017/03/06 10:06PM, Masami Hiramatsu wrote: > On Mon, 6 Mar 2017 23:19:09 +0530 > "Naveen N. Rao" wrote: > > > Masami, > > Your patch works, thanks! However, I felt we could refactor and reuse > > some of the code across kprobes.c for this purpose. Can you

Re: [PATCH] selftests/powerpc: Replace stxvx and lxvx with their equivalent instruction

On 07-Mar-2017 11:43 AM, "Cyril Bur" wrote: On POWER8 (ISA 2.07) lxvx and stxvx are defined to be extended mnemonics of lxvd2x and stxvd2x. For POWER9 (ISA 3.0) the HW architects in their infinite wisdom made lxvx and stxvx instructions in their own right. POWER9 aware GCC

Re: [PATCH v2 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

On Tue, Mar 07, 2017 at 03:28:17PM +0530, Madhavan Srinivasan wrote: > > > On Monday 06 March 2017 04:52 PM, Peter Zijlstra wrote: > >On Mon, Mar 06, 2017 at 04:13:08PM +0530, Madhavan Srinivasan wrote: > >>From: Sukadev Bhattiprolu > >> > >>perf_mem_data_src is an

open list?

scripts/get_maintainers.pl says this is an open list; linuxppc-dev@lists.ozlabs.org (open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)) Patches I've sent with this list cc'd have not been getting through. I resent one to check if it was a user error at my end. This email will obviously serve as

Re: [PATCH v2 1/6] powerpc/perf: Define big-endian version of perf_mem_data_src

On Monday 06 March 2017 04:52 PM, Peter Zijlstra wrote: On Mon, Mar 06, 2017 at 04:13:08PM +0530, Madhavan Srinivasan wrote: From: Sukadev Bhattiprolu perf_mem_data_src is an union that is initialized via the ->val field and accessed via the bitmap fields. For

[RESEND PATCH] powerpc/pseries: move struct hcall_stats to c file

struct hcall_stats is only used in hvCall_inst.c. Move struct hcall_stats to hvCall_inst.c Resolves: #54 Signed-off-by: Tobin C. Harding --- Is this correct, adding 'Resolves: #XX' when fixing github.com/linuxppc/linux issues? arch/powerpc/include/asm/hvcall.h| 10

Re: [PATCH v5 00/15] livepatch: hybrid consistency model

* Josh Poimboeuf wrote: > arch/Kconfig | 6 + > arch/powerpc/include/asm/thread_info.h | 4 +- > arch/powerpc/kernel/signal.c | 4 + > arch/s390/include/asm/thread_info.h | 24 +- >