Hi Ganapatrao,
[auto build test ERROR on arm64/for-next/core]
[also build test ERROR on v4.5-rc2 next-20160205]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Ganapatrao-Kulkarni/arm64-numa-ad
Hi Christophe,
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.5-rc2 next-20160205]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Christophe-Leroy/powerpc-8xx-Use-large-p
Instead of defining the local struct vlantag use the standard definition
of vlan_hdr from .
The fields in the definition have different names:
- vlan -> h_vlan_TCI
- subtype -> h_vlan_encapsulated_proto
Signed-off-by: Luis Henriques
---
arch/powerpc/platforms/ps3/gelic_udbg.c | 16 ++
Several network-related data structures are defined in gelic_udbg.
These could be easily dropped and the standard ones defined in network
headers could be used instead.
The 4 patches that follow replace ethernet, vlan, ip and udp
structures in gelic_udbg. Note that this has been compile-tested
on
Instead of defining a local version of struct ethhdr use the standard
definition from .
The fields in the definition have different names:
- dest -> h_dest
- src -> h_source
- type -> h_proto
Signed-off-by: Luis Henriques
---
arch/powerpc/platforms/ps3/gelic_udbg.c | 16 ++--
1
Instead of defining a local version of struct iphdr use the standard
definition from .
Several fields in the definition have different names:
- proto -> protocol
- src -> saddr
- dest -> daddr
- total_length -> tot_len
- checksum -> check
Also, 'ver_len' is composed by 'version' and 'ihl' i
Instead of defining a local version of struct udphdr use the standard
definition from .
The 'src' field is named 'source' in the definition.
Signed-off-by: Luis Henriques
---
arch/powerpc/platforms/ps3/gelic_udbg.c | 10 ++
1 file changed, 2 insertions(+), 8 deletions(-)
diff --git a/
On Sun, 2016-02-07 at 17:38 +, Luis Henriques wrote:
> Instead of defining a local version of struct ethhdr use the standard
> definition from .
trivia:
> diff --git a/arch/powerpc/platforms/ps3/gelic_udbg.c
> b/arch/powerpc/platforms/ps3/gelic_udbg.c
[]
> @@ -173,8 +169,8 @@ static void gel
On Thu, Feb 04, 2016 at 04:41:10PM +0530, Anshuman Khandual wrote:
> On 02/02/2016 06:28 AM, David Gibson wrote:
> > On Mon, Feb 01, 2016 at 12:41:31PM +0530, Anshuman Khandual wrote:
> >> On 01/29/2016 10:54 AM, David Gibson wrote:
> >>> This adds the hypercall numbers and wrapper functions for th
Frederic Barrat writes:
> --- a/Documentation/ABI/testing/sysfs-class-cxl
> +++ b/Documentation/ABI/testing/sysfs-class-cxl
> @@ -183,7 +183,7 @@ Description:read only
> Identifies the revision level of the PSL.
> Users: https://github.com/ibm-capi/libcxl
>
>
The comment block above pcibios_set_pcie_reset_state() incorrectly refers
to pcibios_set_pcie_slot_reset(). Fix the comment accordingly.
Signed-off-by: Andrew Donnellan
---
arch/powerpc/kernel/eeh.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/powerpc/kernel/eeh.c b/a
On Mon, Feb 08, 2016 at 02:39:19PM +1100, Andrew Donnellan wrote:
>The comment block above pcibios_set_pcie_reset_state() incorrectly refers
>to pcibios_set_pcie_slot_reset(). Fix the comment accordingly.
>
>Signed-off-by: Andrew Donnellan
Acked-by: Gavin Shan
Thanks,
Gavin
>---
> arch/powerpc
"p5ioc2 is used by approximately 2 machines in the world, and has never
ever been a supported configuration."
The code for p5ioc2 is essentially unused and complicates what is already
a very complicated codebase. Its removal is essentially a "free win" in
the effort to simplify the powernv PCI co
On Mon, Feb 08, 2016 at 03:08:20PM +1100, Russell Currey wrote:
>"p5ioc2 is used by approximately 2 machines in the world, and has never
>ever been a supported configuration."
>
>The code for p5ioc2 is essentially unused and complicates what is already
>a very complicated codebase. Its removal is
The EEH debugfs handlers have same prototype. This introduces
a macro to define them, then to simplify the code. No logical
changes.
Signed-off-by: Gavin Shan
---
arch/powerpc/platforms/powernv/eeh-powernv.c | 60 ++--
1 file changed, 22 insertions(+), 38 deletions(-)
di
The original implementation is ugly: unnecessary if statements and
"out" tag. This reworks the function to avoid above weaknesses. No
functional changes introduced.
Signed-off-by: Gavin Shan
---
arch/powerpc/kernel/eeh_pe.c | 28
1 file changed, 12 insertions(+), 16
On Fri, Jan 29, 2016 at 04:23:55PM +1100, David Gibson wrote:
> At the moment memblock_phys_mem_size() is marked as __init, and so is
> discarded after boot. This is different from most of the memblock
> functions which are marked __init_memblock, and are only discarded after
> boot if memory hotp
On Fri, Jan 29, 2016 at 04:23:57PM +1100, David Gibson wrote:
> At the moment the hpte_removebolted callback in ppc_md returns void and
> will BUG_ON() if the hpte it's asked to remove doesn't exist in the first
> place. This is awkward for the case of cleaning up a mapping which was
> partially m
On Fri, Jan 29, 2016 at 04:23:58PM +1100, David Gibson wrote:
> This makes a number of cleanups to handling of mapping failures during
> memory hotplug on Power:
>
> For errors creating the linear mapping for the hot-added region:
> * This is now reported with EFAULT which is more appropriate th
On Fri, Jan 29, 2016 at 04:23:56PM +1100, David Gibson wrote:
> Currently, the only error that htab_remove_mapping() can report is -EINVAL,
> if removal of bolted HPTEs isn't implemeted for this platform. We make
> a few clean ups to the handling of this:
>
> * EINVAL isn't really the right code
"Kirill A. Shutemov" writes:
> On Fri, Feb 05, 2016 at 11:41:40PM +0530, Aneesh Kumar K.V wrote:
>> With ppc64 we use the deposted pgtable_t to store the hash pte slot
>> information. We should not withdraw the deposited pgtable_t without
>> marking the pmd none. This ensure that low level hash f
On 08/02/16 16:35, Gavin Shan wrote:
The original implementation is ugly: unnecessary if statements and
"out" tag. This reworks the function to avoid above weaknesses. No
functional changes introduced.
Signed-off-by: Gavin Shan
This is definitely a lot nicer to read and doesn't appear to have
On Thu, Feb 04, 2016 at 04:26:20PM +0530, Anshuman Khandual wrote:
> On 02/02/2016 06:34 AM, David Gibson wrote:
> > On Mon, Feb 01, 2016 at 12:34:32PM +0530, Anshuman Khandual wrote:
> >> On 01/29/2016 10:53 AM, David Gibson wrote:
> >>> htab_get_table_size() either retrieve the size of the hash p
On Fri, Jan 29, 2016 at 04:24:01PM +1100, David Gibson wrote:
> This adds support for using experimental hypercalls to change the size
> of the main hash page table while running as a PAPR guest. For now these
> hypercalls are only in experimental qemu versions.
>
> The interface is two part: fir
On Fri, Jan 29, 2016 at 04:24:00PM +1100, David Gibson wrote:
> This adds the hypercall numbers and wrapper functions for the hash page
> table resizing hypercalls.
>
> These are experimental "platform specific" values for now, until we have a
> formal PAPR update.
>
> It also adds a new firmware
On Fri, Jan 29, 2016 at 04:24:02PM +1100, David Gibson wrote:
> The hypervisor needs to know a guest is capable of using the HPT resizing
> PAPR extension in order to make full advantage of it for memory hotplug.
>
> If the hypervisor knows the guest is HPT resize aware, it can size the
> initial
On Fri, Jan 29, 2016 at 04:24:03PM +1100, David Gibson wrote:
> We've now implemented code in the pseries platform to use the new PAPR
> interface to allow resizing the hash page table (HPT) at runtime.
>
> This patch uses that interface to automatically attempt to resize the HPT
> when memory is
With ppc64 we use the deposited pgtable_t to store the hash pte slot
information. We should not withdraw the deposited pgtable_t without
marking the pmd none. This ensure that low level hash fault handling
will skip this huge pte and we will handle them at upper levels.
Recent change to pmd splitt
Russell Currey writes:
> "p5ioc2 is used by approximately 2 machines in the world, and has never
> ever been a supported configuration."
>
> The code for p5ioc2 is essentially unused and complicates what is already
> a very complicated codebase. Its removal is essentially a "free win" in
> the e
On Mon, Feb 08, 2016 at 11:44:22AM +0530, Aneesh Kumar K.V wrote:
> With ppc64 we use the deposited pgtable_t to store the hash pte slot
> information. We should not withdraw the deposited pgtable_t without
> marking the pmd none. This ensure that low level hash fault handling
> will skip this huge
30 matches
Mail list logo
