With lazy interrupt, we always call __check_irq_replaysome with
decrementers_next_tb to check if we need to replay timer interrupt.
So in hotplug case we also need to set decrementers_next_tb as MAX
to make sure __check_irq_replay don't replay timer interrupt
when return as we expect, otherwise we'
Please ignore this to check next version.
Tiejun
On 01/15/2013 06:31 PM, Tiejun Chen wrote:
With lazy interrupt, some implementations of hotplug will
get some interrupts even while offline, just ignore these.
Signed-off-by: Tiejun Chen
---
arch/powerpc/kernel/irq.c |6 ++
1 file ch
On 01/16/2013 06:26 AM, Julian Calaby wrote:
Hi Tang,
One minor point.
/*
- * Search memmap entry
+ * firmware_map_find_entry: Search memmap entry.
+ * @start: Start of the memory range.
+ * @end: End of the memory range (exclusive).
+ * @type: Type of the memory range.
+ *
+ * This func
On Tue, Jan 15, 2013 at 10:03:46PM +0800, Shawn Guo wrote:
> On Tue, Jan 15, 2013 at 10:29:33AM +0800, Peter Chen wrote:
> > As mach/hardware.h is deleted, we need to use platform_device_id to
> > differentiate SoCs. Besides, one cpu_is_mx35 is useless as it has
> > already used pdata to differenti
On Tue, Jan 15, 2013 at 03:57:59PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Jan 09, 2013 at 05:07:03PM -0800, Sukadev Bhattiprolu escreveu:
> > [PATCH 6/6][v3] perf: Document the ABI of perf sysfs entries
> >
> > This patchset addes two new sets of files to sysfs:
> >
> > - generic an
Em Wed, Jan 09, 2013 at 05:07:03PM -0800, Sukadev Bhattiprolu escreveu:
> [PATCH 6/6][v3] perf: Document the ABI of perf sysfs entries
>
> This patchset addes two new sets of files to sysfs:
>
> - generic and POWER-specific perf events in /sys/devices/cpu/events/
> - perf event config
When i connect my 500GB seagate HD on a P5020DS, its not getting mounted.
This is the dmesg log;
am i supposed to change some configuration ?
/ # dmesg
usb 1-1: new high speed USB device using fsl-ehci and address 5
usb 1-1: configuration #1 chosen from 1 choice
scsi2 : SCSI emulation for USB Ma
Hi Tang,
One minor point.
On Tue, Jan 15, 2013 at 9:54 PM, Tang Chen wrote:
> It is unsafe to return an entry pointer and release the map_entries_lock. So
> we should
> not hold the map_entries_lock separately in firmware_map_find_entry() and
> firmware_map_remove_entry(). Hold the map_entries_
From: Timur Tabi
The Freescale DIU driver was recently updated to not require a
set_monitor_port platform function if there is only one monitor port. This
is the case on the P1022 RDK and the MPC5121 ADS boards. So now we can
remove those functions.
Signed-off-by: Timur Tabi
---
arch/powerpc
On Fri, 2013-01-11 at 17:29 +1100, Alexey Kardashevskiy wrote:
> +static unsigned long get_user_dscr(struct task_struct *task)
> +{
> + return -EIO;
> +}
> +
Does it make sense to return an error here ? ptrace_get_reg() doesn't
seem to have provisions for returning errors, it just return reg
On Tue, Jan 15, 2013 at 10:29:33AM +0800, Peter Chen wrote:
> As mach/hardware.h is deleted, we need to use platform_device_id to
> differentiate SoCs. Besides, one cpu_is_mx35 is useless as it has
> already used pdata to differentiate runtime
>
> Meanwhile we update the platform code accordingly.
Now we don't free firmware_map_entry which is allocated by bootmem because
there is no way to do so when the system is up. But we can at least remember
the address of that memory and reuse the storage when the memory is added
next time.
This patch introduces a new list map_entries_bootmem to link
When we split a larger page into smaller ones, we should not free them
one by one because only the _count of the first page struct makes sense.
Otherwise, the kernel will panic.
So fulfill the unused small pages with 0xFD, and when the whole larger
page is fulfilled with 0xFD, free the whole large
Direct mapped pages were freed when they were offlined, or they were
not allocated. So we only need to free vmemmap pages, no need to free
direct mapped pages.
Signed-off-by: Tang Chen
---
arch/x86/mm/init_64.c |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/arch
Now we have a map_entries_lock to protect map_entries list.
So we need to update the comments.
Signed-off-by: Tang Chen
---
drivers/firmware/memmap.c |6 +-
1 files changed, 1 insertions(+), 5 deletions(-)
diff --git a/drivers/firmware/memmap.c b/drivers/firmware/memmap.c
index 940c4e9.
It is unsafe to return an entry pointer and release the map_entries_lock. So we
should
not hold the map_entries_lock separately in firmware_map_find_entry() and
firmware_map_remove_entry(). Hold the map_entries_lock across find and remove
/sys/firmware/memmap/X operation.
And also, users of these
We only need to update direct_pages_count[level] when we freeing direct mapped
pagetables.
Signed-off-by: Tang Chen
---
arch/x86/mm/init_64.c | 17 +++--
1 files changed, 7 insertions(+), 10 deletions(-)
diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
index e829113..368
Hi Andrew,
Here are some bug fix patches for physical hot-remove patches.
And there are some new ones reported by others, I'll fix them soon.
Thanks. :)
Tang Chen (6):
Bug fix: Hold spinlock across find|remove /sys/firmware/memmap/X
operation.
Bug fix: Do not calculate direct mapping pa
With lazy interrupt, some implementations of hotplug will
get some interrupts even while offline, just ignore these.
Signed-off-by: Tiejun Chen
---
arch/powerpc/kernel/irq.c |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/powerpc/kernel/irq.c b/arch/powerpc/kernel/irq.c
index 4
On 15/01/13 08:11, ternaryd wrote:
> Hi,
>
> I'm trying to install linux on an e500v2 board with the tsi148
> VME-Bridge, but got stuck. Now it seems that I need to include
> information regarding this bridge into the .dts-file, but can't figure
> out how. Maybe somebody on this list could post th
Hi,
I'm trying to install linux on an e500v2 board with the tsi148
VME-Bridge, but got stuck. Now it seems that I need to include
information regarding this bridge into the .dts-file, but can't figure
out how. Maybe somebody on this list could post the tsi148-specific
part of a device tree, which
Multiple MSI only requires the IRQ in msi_desc entry to be set as
the value of irq_base.
This patch implements the above mentioned technique.
Signed-off-by: Mike Qiu
---
include/linux/irq.h |2 ++
kernel/irq/chip.c | 40 ++--
2 files changed, 32 inser
PCI devices support MSI, MSIX as well as multiple MSI.
But pSeries does not support multiple MSI yet.
This patch enable multiple MSI feature in pSeries.
Signed-off-by: Mike Qiu
---
arch/powerpc/kernel/msi.c|4 --
arch/powerpc/platforms/pseries/msi.c | 62 ++
Adding a function irq_create_mapping_many() which can associate
multiple MSIs to a continous irq mapping.
This is needed to enable multiple MSI support for pSeries.
Signed-off-by: Mike Qiu
---
include/linux/irq.h |2 +
include/linux/irqdomain.h |3 ++
kernel/irq/irqdomain.c|
Currently, multiple MSI feature hasn't been enabled in pSeries,
These patches try to enbale this feature.
These patches have been tested by using ipr driver, and the driver patch
has been made by Wen Xiong :
[PATCH 0/7] Add support for new IBM SAS controllers
Test platform: One partition of pSer
25 matches
Mail list logo
