Re: [PATCH v3 1/2] arm64/efi: report unexpected errors when determining Secure Boot status

On 3 March 2016 at 22:45, Linn Crosetto wrote: > Certain code in the boot path may require the ability to determine whether > UEFI Secure Boot is definitely enabled, for example printing status to the > console. Other code may need to know when UEFI Secure Boot is definitely >

Re: [PATCH v3 1/2] arm64/efi: report unexpected errors when determining Secure Boot status

On 3 March 2016 at 22:45, Linn Crosetto wrote: > Certain code in the boot path may require the ability to determine whether > UEFI Secure Boot is definitely enabled, for example printing status to the > console. Other code may need to know when UEFI Secure Boot is definitely > disabled, for

Re: [Qemu-devel] [RFC qemu 0/4] A PV solution for live migration optimization

On Thu, Mar 03, 2016 at 05:46:15PM +, Dr. David Alan Gilbert wrote: > * Liang Li (liang.z...@intel.com) wrote: > > The current QEMU live migration implementation mark the all the > > guest's RAM pages as dirtied in the ram bulk stage, all these pages > > will be processed and that takes quit a

Re: [Qemu-devel] [RFC qemu 0/4] A PV solution for live migration optimization

On Thu, Mar 03, 2016 at 05:46:15PM +, Dr. David Alan Gilbert wrote: > * Liang Li (liang.z...@intel.com) wrote: > > The current QEMU live migration implementation mark the all the > > guest's RAM pages as dirtied in the ram bulk stage, all these pages > > will be processed and that takes quit a

Re: [PATCH 3/4] leds: Add driver for the ISSI IS31FL32xx family of LED controllers

On 03/04/2016 01:45 AM, David Rivshin (Allworx) wrote: On Thu, 03 Mar 2016 15:51:32 +0100 Jacek Anaszewski wrote: Hi David, Thanks for the update. Two remarks in the code. On 03/03/2016 04:01 AM, David Rivshin (Allworx) wrote: From: David Rivshin

Re: [PATCH 3/4] leds: Add driver for the ISSI IS31FL32xx family of LED controllers

On 03/04/2016 01:45 AM, David Rivshin (Allworx) wrote: On Thu, 03 Mar 2016 15:51:32 +0100 Jacek Anaszewski wrote: Hi David, Thanks for the update. Two remarks in the code. On 03/03/2016 04:01 AM, David Rivshin (Allworx) wrote: From: David Rivshin The IS31FL32xx family of LED controllers

Re: [PATCH 0/3] OOM detection rework v4

On Thu, Mar 03, 2016 at 01:54:43AM -0800, Hugh Dickins wrote: > On Tue, 1 Mar 2016, Michal Hocko wrote: > > [Adding Vlastimil and Joonsoo for compaction related things - this was a > > large thread but the more interesting part starts with > >

Re: [PATCH 0/3] OOM detection rework v4

On Thu, Mar 03, 2016 at 01:54:43AM -0800, Hugh Dickins wrote: > On Tue, 1 Mar 2016, Michal Hocko wrote: > > [Adding Vlastimil and Joonsoo for compaction related things - this was a > > large thread but the more interesting part starts with > >

linux-next: manual merge of the akpm-current tree with the powerpc tree

Hi all, Today's linux-next merge of the akpm-current tree got a conflict in: mm/huge_memory.c between commit: ff20c2e0acc5 ("mm: Some arch may want to use HPAGE_PMD related values as variables") from the powerpc tree and commit: 82fdbe051e29 ("mm: make optimistic check for swapin

linux-next: manual merge of the akpm-current tree with the powerpc tree

Hi all, Today's linux-next merge of the akpm-current tree got a conflict in: mm/huge_memory.c between commit: ff20c2e0acc5 ("mm: Some arch may want to use HPAGE_PMD related values as variables") from the powerpc tree and commit: 82fdbe051e29 ("mm: make optimistic check for swapin

4.4.3: OOPS when running "stress-ng --sock 5"

Hi, on my system I can reproduce reliably a kernel OOPS when I run stress-ng ("apt-get install stress-ng"). Any help on how to track this down would be appreciated, networking code is outside of my comfort zone (I'm just a dilettante at device drivers ...). It takes only a minute or two to get

4.4.3: OOPS when running "stress-ng --sock 5"

Hi, on my system I can reproduce reliably a kernel OOPS when I run stress-ng ("apt-get install stress-ng"). Any help on how to track this down would be appreciated, networking code is outside of my comfort zone (I'm just a dilettante at device drivers ...). It takes only a minute or two to get

Re: Kernel docs: muddying the waters a bit

On Fri, 04 Mar 2016, Russel Winder wrote: > On Thu, 2016-03-03 at 15:23 -0800, Keith Packard wrote: >>   1) the python version (asciidoc) appears to have been abandoned in >>  favor of the ruby version.  > > This is I think true, however the Java-based tool chain

Re: Kernel docs: muddying the waters a bit

On Fri, 04 Mar 2016, Russel Winder wrote: > On Thu, 2016-03-03 at 15:23 -0800, Keith Packard wrote: >>   1) the python version (asciidoc) appears to have been abandoned in >>  favor of the ruby version.  > > This is I think true, however the Java-based tool chain Asciidoctor is > I believe

Re: [PATCH 0/3] OOM detection rework v4

On 03/03/2016 09:57 PM, Hugh Dickins wrote: > >> >> I do not have an explanation why it would cause oom sooner but this >> turned out to be incomplete. There is another wmaark check deeper in the >> compaction path. Could you try the one from >>

Re: [PATCH 0/3] OOM detection rework v4

On 03/03/2016 09:57 PM, Hugh Dickins wrote: > >> >> I do not have an explanation why it would cause oom sooner but this >> turned out to be incomplete. There is another wmaark check deeper in the >> compaction path. Could you try the one from >>

[PATCH v5 2/3] gpio: designware: add acpi binding

This patch adds acpi binding for designware gpio driver, because it is used to support power button on hisilicon d02 board. These two bindings, DT and acpi, are compatible in this driver. Reviewed-by: Andy Shevchenko Acked-by: Mika Westerberg

[PATCH v5 3/3] gpio: designware: add gpio-signaled acpi event support

This patch adds the support for the gpio-signaled acpi event. This is used for power button on hisilicon D02 board, which is an arm64 platform. To support this function, _AEI and _Exx objects must be defined in the corresponding GPIO device as follows: Name (_AEI, ResourceTemplate () {

[PATCH v5 2/3] gpio: designware: add acpi binding

This patch adds acpi binding for designware gpio driver, because it is used to support power button on hisilicon d02 board. These two bindings, DT and acpi, are compatible in this driver. Reviewed-by: Andy Shevchenko Acked-by: Mika Westerberg Signed-off-by: qiujiang ---

[PATCH v5 3/3] gpio: designware: add gpio-signaled acpi event support

This patch adds the support for the gpio-signaled acpi event. This is used for power button on hisilicon D02 board, which is an arm64 platform. To support this function, _AEI and _Exx objects must be defined in the corresponding GPIO device as follows: Name (_AEI, ResourceTemplate () {

[PATCH v5 0/3] "gpio: designware: add gpio-signaled acpi event support for power button"

This patchset adds gpio-signaled acpi events support for power button on hisilicon D02 board. The three patches respectively: - convert device node to fwnode - add acpi binding - add gpio-signaled acpi event support This patchset is based on

[PATCH v5 1/3] gpio: designware: convert device node to fwnode

This patch converts device node to fwnode in dwapb_port_property for designware gpio driver, so as to provide a unified data structure for DT and ACPI bindings. Acked-by: Andy Shevchenko Signed-off-by: qiujiang --- drivers/gpio/gpio-dwapb.c

[PATCH v5 0/3] "gpio: designware: add gpio-signaled acpi event support for power button"

This patchset adds gpio-signaled acpi events support for power button on hisilicon D02 board. The three patches respectively: - convert device node to fwnode - add acpi binding - add gpio-signaled acpi event support This patchset is based on

[PATCH v5 1/3] gpio: designware: convert device node to fwnode

This patch converts device node to fwnode in dwapb_port_property for designware gpio driver, so as to provide a unified data structure for DT and ACPI bindings. Acked-by: Andy Shevchenko Signed-off-by: qiujiang --- drivers/gpio/gpio-dwapb.c| 43 +++-

Re: Suspicious error for CMA stress test

On 2016/3/4 14:38, Joonsoo Kim wrote: > On Fri, Mar 04, 2016 at 02:05:09PM +0800, Hanjun Guo wrote: >> On 2016/3/4 12:32, Joonsoo Kim wrote: >>> On Fri, Mar 04, 2016 at 11:02:33AM +0900, Joonsoo Kim wrote: On Thu, Mar 03, 2016 at 08:49:01PM +0800, Hanjun Guo wrote: > On 2016/3/3 15:42,

Re: Suspicious error for CMA stress test

On 2016/3/4 14:38, Joonsoo Kim wrote: > On Fri, Mar 04, 2016 at 02:05:09PM +0800, Hanjun Guo wrote: >> On 2016/3/4 12:32, Joonsoo Kim wrote: >>> On Fri, Mar 04, 2016 at 11:02:33AM +0900, Joonsoo Kim wrote: On Thu, Mar 03, 2016 at 08:49:01PM +0800, Hanjun Guo wrote: > On 2016/3/3 15:42,

Re: Kernel docs: muddying the waters a bit

On Thu, 2016-03-03 at 15:23 -0800, Keith Packard wrote: > […] > However, I think asciidoc has two serious problems: > >   1) the python version (asciidoc) appears to have been abandoned in >  favor of the ruby version.  This is I think true, however the Java-based tool chain Asciidoctor is

Re: Kernel docs: muddying the waters a bit

On Thu, 2016-03-03 at 15:23 -0800, Keith Packard wrote: > […] > However, I think asciidoc has two serious problems: > >   1) the python version (asciidoc) appears to have been abandoned in >  favor of the ruby version.  This is I think true, however the Java-based tool chain Asciidoctor is

Re: [PATCH] KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page()

On 2016年03月04日 15:21, Thomas Gleixner wrote: > On Fri, 4 Mar 2016, Lan Tianyu wrote: > >> The following kvm_flush_remote_tlbs() will call smp_mb() inside and so >> remove smp_mb() here. >> >> Signed-off-by: Lan Tianyu >> --- >> arch/x86/kvm/mmu.c | 6 -- >> 1 file

Re: [PATCH] KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page()

On 2016年03月04日 15:21, Thomas Gleixner wrote: > On Fri, 4 Mar 2016, Lan Tianyu wrote: > >> The following kvm_flush_remote_tlbs() will call smp_mb() inside and so >> remove smp_mb() here. >> >> Signed-off-by: Lan Tianyu >> --- >> arch/x86/kvm/mmu.c | 6 -- >> 1 file changed, 6 deletions(-) >>

Re: [PATCH] KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page()

On Fri, 4 Mar 2016, Lan Tianyu wrote: > The following kvm_flush_remote_tlbs() will call smp_mb() inside and so > remove smp_mb() here. > > Signed-off-by: Lan Tianyu > --- > arch/x86/kvm/mmu.c | 6 -- > 1 file changed, 6 deletions(-) > > diff --git

Re: [PATCH] KVM: Remove redundant smp_mb() in the kvm_mmu_commit_zap_page()

On Fri, 4 Mar 2016, Lan Tianyu wrote: > The following kvm_flush_remote_tlbs() will call smp_mb() inside and so > remove smp_mb() here. > > Signed-off-by: Lan Tianyu > --- > arch/x86/kvm/mmu.c | 6 -- > 1 file changed, 6 deletions(-) > > diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c

Re: [PATCH 2/5] usb: gadget: f_midi: added spinlock on transmit function

Hi, "Felipe F. Tonello" writes: > [ text/plain ] > Since f_midi_transmit is called by both ALSA and USB frameworks, it can > potentially cause a race condition between both calls. This is bad because the > way f_midi_transmit is implemented can't handle concurrent calls.

Re: [PATCH 2/5] usb: gadget: f_midi: added spinlock on transmit function

Hi, "Felipe F. Tonello" writes: > [ text/plain ] > Since f_midi_transmit is called by both ALSA and USB frameworks, it can > potentially cause a race condition between both calls. This is bad because the > way f_midi_transmit is implemented can't handle concurrent calls. This is due > to the

[PATCH] stmmac: Fix type of local variable in stmmac_xmit

Variable entry holds result of jumbo_frm callback. It can be negative, so the variable should be signed. The patch changes also type of related first_entry variable to make code compact and coherent. The problem has been detected using patch

[PATCH] stmmac: Fix type of local variable in stmmac_xmit

Variable entry holds result of jumbo_frm callback. It can be negative, so the variable should be signed. The patch changes also type of related first_entry variable to make code compact and coherent. The problem has been detected using patch

Re: [PATCH 3/5] usb: gadget: gmidi: remove bus powered requirement on bmAttributes

Hi, "Felipe F. Tonello" writes: > [ text/plain ] > This gadget uses a bmAttributes and MaxPower that requires the USB bus to be > powered from the host, which is not correct because this configuration is > device > specific, not a USB-MIDI requirement. > > This patch

Re: [PATCH 3/5] usb: gadget: gmidi: remove bus powered requirement on bmAttributes

Hi, "Felipe F. Tonello" writes: > [ text/plain ] > This gadget uses a bmAttributes and MaxPower that requires the USB bus to be > powered from the host, which is not correct because this configuration is > device > specific, not a USB-MIDI requirement. > > This patch adds two modules

Re: [PATCH 4/5] usb: gadget: f_midi: cleanups and typos fixes

"Felipe F. Tonello" writes: > [ text/plain ] > Signed-off-by: Felipe F. Tonello no commit log == no commit -- balbi signature.asc Description: PGP signature

Re: [PATCH 4/5] usb: gadget: f_midi: cleanups and typos fixes

"Felipe F. Tonello" writes: > [ text/plain ] > Signed-off-by: Felipe F. Tonello no commit log == no commit -- balbi signature.asc Description: PGP signature

Re: [PATCH 5/5] usb: gadget: f_midi: updated copyright

"Felipe F. Tonello" writes: > [ text/plain ] > Signed-off-by: Felipe F. Tonello no commit log == no commit > --- > drivers/usb/gadget/function/f_midi.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git

Re: [PATCH 5/5] usb: gadget: f_midi: updated copyright

"Felipe F. Tonello" writes: > [ text/plain ] > Signed-off-by: Felipe F. Tonello no commit log == no commit > --- > drivers/usb/gadget/function/f_midi.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/drivers/usb/gadget/function/f_midi.c > b/drivers/usb/gadget/function/f_midi.c >

Re: [PATCH 0/5] MIDI USB Gadget improvements

Hi, "Felipe F. Tonello" writes: > [ text/plain ] > Patches are pretty much self-described. > > Patch 1 is revised from comments. you really need to describe what you changed. This also should have v2 on subject line. I guess it's too late to get this in v4.6 merge

Re: [PATCH 0/5] MIDI USB Gadget improvements

Hi, "Felipe F. Tonello" writes: > [ text/plain ] > Patches are pretty much self-described. > > Patch 1 is revised from comments. you really need to describe what you changed. This also should have v2 on subject line. I guess it's too late to get this in v4.6 merge window as I'm already

Re: [PATCH v4 18/18] i2c-mux: relax locking of the top i2c adapter during i2c controlled muxing

Hi! Here's a fixup for a problem found by the test robot. Sorry for the inconvenience. Cheers, Peter diff --git a/drivers/i2c/i2c-mux.c b/drivers/i2c/i2c-mux.c index 40a4e0397826..b73c42eddca3 100644 --- a/drivers/i2c/i2c-mux.c +++ b/drivers/i2c/i2c-mux.c @@ -226,6 +226,7 @@ struct i2c_adapter

Re: [PATCH v4 18/18] i2c-mux: relax locking of the top i2c adapter during i2c controlled muxing

Hi! Here's a fixup for a problem found by the test robot. Sorry for the inconvenience. Cheers, Peter diff --git a/drivers/i2c/i2c-mux.c b/drivers/i2c/i2c-mux.c index 40a4e0397826..b73c42eddca3 100644 --- a/drivers/i2c/i2c-mux.c +++ b/drivers/i2c/i2c-mux.c @@ -226,6 +226,7 @@ struct i2c_adapter

Re: [PATCH 0/3] OOM detection rework v4

On Thu, Mar 03, 2016 at 04:50:16PM +0100, Vlastimil Babka wrote: > On 03/03/2016 03:10 PM, Joonsoo Kim wrote: > > > >> [...] > > At least, reset no_progress_loops when did_some_progress. High > > order allocation up to PAGE_ALLOC_COSTLY_ORDER is as important > > as order 0. And,

Re: [PATCH 0/3] OOM detection rework v4

On Thu, Mar 03, 2016 at 04:50:16PM +0100, Vlastimil Babka wrote: > On 03/03/2016 03:10 PM, Joonsoo Kim wrote: > > > >> [...] > > At least, reset no_progress_loops when did_some_progress. High > > order allocation up to PAGE_ALLOC_COSTLY_ORDER is as important > > as order 0. And,

Re: [PATCH v2] media: platform: Add missing MFD_SYSCON dependency on HAS_IOMEM

On 04.03.2016 16:03, Holger Schurig wrote: > Krzysztof Kozlowski writes: > >> +depends on HAS_IOMEM# For MFD_SYSCON > > > I think this comment is not necessary, it's also highly unusual. On > other words: other

Re: [PATCH v2] media: platform: Add missing MFD_SYSCON dependency on HAS_IOMEM

On 04.03.2016 16:03, Holger Schurig wrote: > Krzysztof Kozlowski writes: > >> +depends on HAS_IOMEM# For MFD_SYSCON > > > I think this comment is not necessary, it's also highly unusual. On > other words: other patches like this don't add

Re: [PATCH v2] media: platform: Add missing MFD_SYSCON dependency on HAS_IOMEM

Krzysztof Kozlowski writes: > + depends on HAS_IOMEM# For MFD_SYSCON I think this comment is not necessary, it's also highly unusual. On other words: other patches like this don't add such comments. You can always

Re: [PATCH v2] media: platform: Add missing MFD_SYSCON dependency on HAS_IOMEM

Krzysztof Kozlowski writes: > + depends on HAS_IOMEM# For MFD_SYSCON I think this comment is not necessary, it's also highly unusual. On other words: other patches like this don't add such comments. You can always use "git blame" to find out

Re: Suspicious error for CMA stress test

On 2016/3/4 10:02, Joonsoo Kim wrote: > On Thu, Mar 03, 2016 at 08:49:01PM +0800, Hanjun Guo wrote: >> On 2016/3/3 15:42, Joonsoo Kim wrote: >>> 2016-03-03 10:25 GMT+09:00 Laura Abbott : (cc -mm and Joonsoo Kim) On 03/02/2016 05:52 AM, Hanjun Guo wrote:

Re: Suspicious error for CMA stress test

On 2016/3/4 10:02, Joonsoo Kim wrote: > On Thu, Mar 03, 2016 at 08:49:01PM +0800, Hanjun Guo wrote: >> On 2016/3/3 15:42, Joonsoo Kim wrote: >>> 2016-03-03 10:25 GMT+09:00 Laura Abbott : (cc -mm and Joonsoo Kim) On 03/02/2016 05:52 AM, Hanjun Guo wrote: > Hi, > > I

[PATCH] ASoC: rt5616: allow to build with CONFIG_SND_SOC_RT5616

This patch fixes that hasn't built the rt5616 driver with 'CONFIG_SND_SOC_RT5616=y' in .config. The tristate is the prompt on the 'make menuconfig', in other words, that can't show the prompt and select it if we don't say what's the tristate. Signed-off-by: Caesar Wang ---

[PATCH] ASoC: rt5616: allow to build with CONFIG_SND_SOC_RT5616

This patch fixes that hasn't built the rt5616 driver with 'CONFIG_SND_SOC_RT5616=y' in .config. The tristate is the prompt on the 'make menuconfig', in other words, that can't show the prompt and select it if we don't say what's the tristate. Signed-off-by: Caesar Wang ---

Re: [PATCH 1/4] scatterlist: Introduce some helper functions

>>> + **/ >>> +static inline bool sg_is_contiguous(struct scatterlist *sga, >>> + struct scatterlist *sgb) >>> +{ >>> + return ((sga->page_link & ~0x3UL) + sga->offset + sga->length == >>> + (sgb->page_link & ~0x3UL)); >>> +} >> I don't understand

Re: [PATCH 1/4] scatterlist: Introduce some helper functions

>>> + **/ >>> +static inline bool sg_is_contiguous(struct scatterlist *sga, >>> + struct scatterlist *sgb) >>> +{ >>> + return ((sga->page_link & ~0x3UL) + sga->offset + sga->length == >>> + (sgb->page_link & ~0x3UL)); >>> +} >> I don't understand

Re: [PATCH v2 2/2] mmc: sdhci-tegra: Specify valid DMA mask

On Fri, Mar 4, 2016 at 3:08 PM, Alexandre Courbot wrote: > On Wed, Mar 2, 2016 at 8:25 PM, Arnd Bergmann wrote: >> On Wednesday 02 March 2016 19:36:23 Alexandre Courbot wrote: >>> On Wed, Mar 2, 2016 at 6:34 AM, Arnd Bergmann wrote: >>> > On

Re: [PATCH v2 2/2] mmc: sdhci-tegra: Specify valid DMA mask

On Fri, Mar 4, 2016 at 3:08 PM, Alexandre Courbot wrote: > On Wed, Mar 2, 2016 at 8:25 PM, Arnd Bergmann wrote: >> On Wednesday 02 March 2016 19:36:23 Alexandre Courbot wrote: >>> On Wed, Mar 2, 2016 at 6:34 AM, Arnd Bergmann wrote: >>> > On Tuesday 01 March 2016 13:32:44 Alexandre Courbot

[PATCH v5 10/17] arm/xen: Get event-channel irq through HVM_PARAM when booting with ACPI

From: Shannon Zhao When booting with ACPI, it could get the event-channel irq through HVM_PARAM_CALLBACK_IRQ. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini --- arch/arm/xen/enlighten.c | 36

[PATCH v5 03/17] Xen: xlate: Use page_to_xen_pfn instead of page_to_pfn

From: Shannon Zhao Make xen_xlate_map_ballooned_pages work with 64K pages. In that case Kernel pages are 64K in size but Xen pages remain 4K in size. Xen pfns refer to 4K pages. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini

[PATCH v5 03/17] Xen: xlate: Use page_to_xen_pfn instead of page_to_pfn

From: Shannon Zhao Make xen_xlate_map_ballooned_pages work with 64K pages. In that case Kernel pages are 64K in size but Xen pages remain 4K in size. Xen pfns refer to 4K pages. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini --- drivers/xen/xlate_mmu.c | 26

[PATCH v5 10/17] arm/xen: Get event-channel irq through HVM_PARAM when booting with ACPI

From: Shannon Zhao When booting with ACPI, it could get the event-channel irq through HVM_PARAM_CALLBACK_IRQ. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini --- arch/arm/xen/enlighten.c | 36 +++- 1 file changed, 35 insertions(+), 1 deletion(-)

[PATCH v5 06/17] Xen: ARM: Add support for mapping platform device mmio

From: Shannon Zhao Add a bus_notifier for platform bus device in order to map the device mmio regions when DOM0 booting with ACPI. Signed-off-by: Shannon Zhao Acked-by: Stefano Stabellini ---

[PATCH v5 06/17] Xen: ARM: Add support for mapping platform device mmio

From: Shannon Zhao Add a bus_notifier for platform bus device in order to map the device mmio regions when DOM0 booting with ACPI. Signed-off-by: Shannon Zhao Acked-by: Stefano Stabellini --- drivers/xen/Makefile | 1 + drivers/xen/arm-device.c | 141

[PATCH v5 17/17] Xen: EFI: Parse DT parameters for Xen specific UEFI

From: Shannon Zhao Add a new function to parse DT parameters for Xen specific UEFI just like the way for normal UEFI. Then it could reuse the existing codes. If Xen supports EFI, initialize runtime services. Signed-off-by: Shannon Zhao

[PATCH v5 11/17] ARM: XEN: Move xen_early_init() before efi_init()

From: Shannon Zhao Move xen_early_init() before efi_init(), then when calling efi_init() could initialize Xen specific UEFI. Check if it runs on Xen hypervisor through the flat dts. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini

[PATCH v5 17/17] Xen: EFI: Parse DT parameters for Xen specific UEFI

From: Shannon Zhao Add a new function to parse DT parameters for Xen specific UEFI just like the way for normal UEFI. Then it could reuse the existing codes. If Xen supports EFI, initialize runtime services. Signed-off-by: Shannon Zhao Reviewed-by: Matt Fleming Reviewed-by: Stefano

[PATCH v5 11/17] ARM: XEN: Move xen_early_init() before efi_init()

From: Shannon Zhao Move xen_early_init() before efi_init(), then when calling efi_init() could initialize Xen specific UEFI. Check if it runs on Xen hypervisor through the flat dts. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini --- arch/arm/xen/enlighten.c | 56

[PATCH v5 08/17] Xen: public/hvm: sync changes of HVM_PARAM_CALLBACK_VIA ABI from Xen

From: Shannon Zhao Sync the changes of HVM_PARAM_CALLBACK_VIA ABI introduced by Xen commit (public/hvm: export the HVM_PARAM_CALLBACK_VIA ABI in the API). Signed-off-by: Shannon Zhao Acked-by: Stefano Stabellini

[PATCH v5 07/17] Xen: ARM: Add support for mapping AMBA device mmio

From: Shannon Zhao Add a bus_notifier for AMBA bus device in order to map the device mmio regions when DOM0 booting with ACPI. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini ---

[PATCH v5 07/17] Xen: ARM: Add support for mapping AMBA device mmio

From: Shannon Zhao Add a bus_notifier for AMBA bus device in order to map the device mmio regions when DOM0 booting with ACPI. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini --- drivers/xen/arm-device.c | 43 +++ 1 file changed, 43

[PATCH v5 08/17] Xen: public/hvm: sync changes of HVM_PARAM_CALLBACK_VIA ABI from Xen

From: Shannon Zhao Sync the changes of HVM_PARAM_CALLBACK_VIA ABI introduced by Xen commit (public/hvm: export the HVM_PARAM_CALLBACK_VIA ABI in the API). Signed-off-by: Shannon Zhao Acked-by: Stefano Stabellini --- include/xen/interface/hvm/params.h | 27 +-- 1 file

Re: [PATCH] sound/usb: Use meaninful names for goto labels

Thanks! regards, dan carpenter

[PATCH v5 14/17] XEN: EFI: Move x86 specific codes to architecture directory

From: Shannon Zhao Move x86 specific codes to architecture directory and export those EFI runtime service functions. This will be useful for initializing runtime service on ARM later. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini

Re: [PATCH] sound/usb: Use meaninful names for goto labels

Thanks! regards, dan carpenter

[PATCH v5 14/17] XEN: EFI: Move x86 specific codes to architecture directory

From: Shannon Zhao Move x86 specific codes to architecture directory and export those EFI runtime service functions. This will be useful for initializing runtime service on ARM later. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini --- arch/x86/xen/efi.c| 112

[PATCH v5 16/17] FDT: Add a helper to get the subnode by given name

From: Shannon Zhao Sometimes it needs to check if there is a subnode of given node in FDT by given name. Introduce this helper to get the subnode if it exists. CC: Rob Herring Signed-off-by: Shannon Zhao --- drivers/of/fdt.c

[PATCH v5 16/17] FDT: Add a helper to get the subnode by given name

From: Shannon Zhao Sometimes it needs to check if there is a subnode of given node in FDT by given name. Introduce this helper to get the subnode if it exists. CC: Rob Herring Signed-off-by: Shannon Zhao --- drivers/of/fdt.c | 13 + include/linux/of_fdt.h | 2 ++ 2 files

[PATCH v5 15/17] ARM64: XEN: Add a function to initialize Xen specific UEFI runtime services

From: Shannon Zhao When running on Xen hypervisor, runtime services are supported through hypercall. Add a Xen specific function to initialize runtime services. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini

[PATCH v5 00/17] Add ACPI support for Xen Dom0 on ARM64

From: Shannon Zhao This patch set adds ACPI support for Xen Dom0 on ARM64. The relevant Xen ACPI on ARM64 design document could be found from [1]. This patch set adds a new FDT node "uefi" under /hypervisor to pass UEFI information. Introduce a bus notifier of AMBA and

[PATCH v5 15/17] ARM64: XEN: Add a function to initialize Xen specific UEFI runtime services

From: Shannon Zhao When running on Xen hypervisor, runtime services are supported through hypercall. Add a Xen specific function to initialize runtime services. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini --- arch/arm/include/asm/xen/xen-ops.h | 6 ++

[PATCH v5 00/17] Add ACPI support for Xen Dom0 on ARM64

From: Shannon Zhao This patch set adds ACPI support for Xen Dom0 on ARM64. The relevant Xen ACPI on ARM64 design document could be found from [1]. This patch set adds a new FDT node "uefi" under /hypervisor to pass UEFI information. Introduce a bus notifier of AMBA and Platform bus to map the

[PATCH v5 13/17] ARM: Xen: Document UEFI support on Xen ARM virtual platforms

From: Shannon Zhao Add a "uefi" node under /hypervisor node in FDT, then Linux kernel could scan this to get the UEFI information. Signed-off-by: Shannon Zhao Acked-by: Rob Herring Reviewed-by: Stefano Stabellini

[PATCH v5 13/17] ARM: Xen: Document UEFI support on Xen ARM virtual platforms

From: Shannon Zhao Add a "uefi" node under /hypervisor node in FDT, then Linux kernel could scan this to get the UEFI information. Signed-off-by: Shannon Zhao Acked-by: Rob Herring Reviewed-by: Stefano Stabellini --- CC: Rob Herring --- Documentation/devicetree/bindings/arm/xen.txt | 33

[PATCH v5 05/17] xen: memory : Add new XENMAPSPACE type XENMAPSPACE_dev_mmio

From: Shannon Zhao Add a new type of Xen map space for Dom0 to map device's MMIO region. Signed-off-by: Shannon Zhao --- include/xen/interface/memory.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/xen/interface/memory.h

[PATCH v5 05/17] xen: memory : Add new XENMAPSPACE type XENMAPSPACE_dev_mmio

From: Shannon Zhao Add a new type of Xen map space for Dom0 to map device's MMIO region. Signed-off-by: Shannon Zhao --- include/xen/interface/memory.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/xen/interface/memory.h b/include/xen/interface/memory.h index 2ecfe4f..9aa8988

[PATCH v5 02/17] xen/grant-table: Move xlated_setup_gnttab_pages to common place

From: Shannon Zhao Move xlated_setup_gnttab_pages to common place, so it can be reused by ARM to setup grant table. Rename it to xen_xlate_map_ballooned_pages. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini

[PATCH v5 12/17] ARM64: ACPI: Check if it runs on Xen to enable or disable ACPI

From: Shannon Zhao When it's a Xen domain0 booting with ACPI, it will supply a /chosen and a /hypervisor node in DT. So check if it needs to enable ACPI. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini

[PATCH v5 02/17] xen/grant-table: Move xlated_setup_gnttab_pages to common place

From: Shannon Zhao Move xlated_setup_gnttab_pages to common place, so it can be reused by ARM to setup grant table. Rename it to xen_xlate_map_ballooned_pages. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini --- arch/x86/xen/grant-table.c | 57

[PATCH v5 12/17] ARM64: ACPI: Check if it runs on Xen to enable or disable ACPI

From: Shannon Zhao When it's a Xen domain0 booting with ACPI, it will supply a /chosen and a /hypervisor node in DT. So check if it needs to enable ACPI. Signed-off-by: Shannon Zhao Reviewed-by: Stefano Stabellini Acked-by: Hanjun Guo --- arch/arm64/kernel/acpi.c | 12 1 file

[PATCH v5 01/17] Xen: ACPI: Hide UART used by Xen

From: Shannon Zhao ACPI 6.0 introduces a new table STAO to list the devices which are used by Xen and can't be used by Dom0. On Xen virtual platforms, the physical UART is used by Xen. So here it hides UART from Dom0. Signed-off-by: Shannon Zhao

[PATCH v5 01/17] Xen: ACPI: Hide UART used by Xen

From: Shannon Zhao ACPI 6.0 introduces a new table STAO to list the devices which are used by Xen and can't be used by Dom0. On Xen virtual platforms, the physical UART is used by Xen. So here it hides UART from Dom0. Signed-off-by: Shannon Zhao --- CC: "Rafael J. Wysocki" (supporter:ACPI)

[PATCH v5 09/17] xen/hvm/params: Add a new delivery type for event-channel in HVM_PARAM_CALLBACK_IRQ

From: Shannon Zhao Add a new delivery type: val[63:56] == 3: val[15:8] is flag: val[7:0] is a PPI. To the flag, bit 0 stands the interrupt mode is edge(1) or level(0) and bit 1 stands the interrupt polarity is active low(1) or high(0). Signed-off-by: Shannon Zhao

[PATCH v5 09/17] xen/hvm/params: Add a new delivery type for event-channel in HVM_PARAM_CALLBACK_IRQ

From: Shannon Zhao Add a new delivery type: val[63:56] == 3: val[15:8] is flag: val[7:0] is a PPI. To the flag, bit 0 stands the interrupt mode is edge(1) or level(0) and bit 1 stands the interrupt polarity is active low(1) or high(0). Signed-off-by: Shannon Zhao Acked-by: Stefano Stabellini

[PATCH v5 04/17] arm/xen: Use xen_xlate_map_ballooned_pages to setup grant table

From: Shannon Zhao Use xen_xlate_map_ballooned_pages to setup grant table. Then it doesn't rely on DT or ACPI to pass the start address and size of grant table. Signed-off-by: Shannon Zhao Acked-by: Stefano Stabellini

[PATCH v5 04/17] arm/xen: Use xen_xlate_map_ballooned_pages to setup grant table

From: Shannon Zhao Use xen_xlate_map_ballooned_pages to setup grant table. Then it doesn't rely on DT or ACPI to pass the start address and size of grant table. Signed-off-by: Shannon Zhao Acked-by: Stefano Stabellini --- arch/arm/xen/enlighten.c | 13 - 1 file changed, 4

Re: Suspicious error for CMA stress test

On Fri, Mar 04, 2016 at 02:05:09PM +0800, Hanjun Guo wrote: > On 2016/3/4 12:32, Joonsoo Kim wrote: > > On Fri, Mar 04, 2016 at 11:02:33AM +0900, Joonsoo Kim wrote: > >> On Thu, Mar 03, 2016 at 08:49:01PM +0800, Hanjun Guo wrote: > >>> On 2016/3/3 15:42, Joonsoo Kim wrote: > 2016-03-03 10:25

Re: Suspicious error for CMA stress test

On Fri, Mar 04, 2016 at 02:05:09PM +0800, Hanjun Guo wrote: > On 2016/3/4 12:32, Joonsoo Kim wrote: > > On Fri, Mar 04, 2016 at 11:02:33AM +0900, Joonsoo Kim wrote: > >> On Thu, Mar 03, 2016 at 08:49:01PM +0800, Hanjun Guo wrote: > >>> On 2016/3/3 15:42, Joonsoo Kim wrote: > 2016-03-03 10:25

  1   2   3   4   5   6   7   8   9   10   >