Re: applied? Re: [PATCH v1 0/2] Update NVMM support to recent changes, [PATCH v1 1/2] Only check CONFIG_NVMM when NEED_CPU_H is defined, [PATCH v1 2/2] Fix nvmm_ram_block_added() function arguments

2021-09-10 Thread Paolo Bonzini
On 07/09/21 18:02, Reinoud Zandijk wrote: ping? Queued, thanks. Paolo On Sun, Aug 29, 2021 at 05:39:07PM +0100, Peter Maydell wrote: On Sun, 29 Aug 2021 at 17:06, Reinoud Zandijk wrote: Hi :) Have these patches been applied? How can I easily check it without manually checking if they ar

Re: [PATCH v1 1/2] Only check CONFIG_NVMM when NEED_CPU_H is defined

2021-09-08 Thread Philippe Mathieu-Daudé
+Thomas On 9/8/21 11:46 AM, Reinoud Zandijk wrote: > On Tue, Sep 07, 2021 at 06:20:33PM +0200, Philippe Mathieu-Daudé wrote: >> On 7/18/21 3:46 PM, Reinoud Zandijk wrote: >>> Userland targers will otherwise use a poisoned CONFIG_NVMM >> >> Typo "targets", but do you mean bsd-user or linux-user? >

Re: [PATCH v1 1/2] Only check CONFIG_NVMM when NEED_CPU_H is defined

2021-09-08 Thread Reinoud Zandijk
On Tue, Sep 07, 2021 at 06:20:33PM +0200, Philippe Mathieu-Daudé wrote: > On 7/18/21 3:46 PM, Reinoud Zandijk wrote: > > Userland targers will otherwise use a poisoned CONFIG_NVMM > > Typo "targets", but do you mean bsd-user or linux-user? Since its on NetBSD, I guess its bsd-user :) > But what

Re: [PATCH v1 1/2] Only check CONFIG_NVMM when NEED_CPU_H is defined

2021-09-07 Thread Philippe Mathieu-Daudé
On 7/18/21 3:46 PM, Reinoud Zandijk wrote: > Userland targers will otherwise use a poisoned CONFIG_NVMM Typo "targets", but do you mean bsd-user or linux-user? But what is the error you get here? cpu_report_tpr_access() is protected for !CONFIG_USER_ONLY, target/i386/nvmm/ is only build on syste

Re: applied? Re: [PATCH v1 0/2] Update NVMM support to recent changes, [PATCH v1 1/2] Only check CONFIG_NVMM when NEED_CPU_H is defined, [PATCH v1 2/2] Fix nvmm_ram_block_added() function arguments

2021-09-07 Thread Reinoud Zandijk
ping? On Sun, Aug 29, 2021 at 05:39:07PM +0100, Peter Maydell wrote: > On Sun, 29 Aug 2021 at 17:06, Reinoud Zandijk wrote: > > > > Hi :) > > > > Have these patches been applied? How can I easily check it without manually > > checking if they are there in a git pullup? Am I notified normally when

Re: applied? Re: [PATCH v1 0/2] Update NVMM support to recent changes, [PATCH v1 1/2] Only check CONFIG_NVMM when NEED_CPU_H is defined, [PATCH v1 2/2] Fix nvmm_ram_block_added() function arguments

2021-08-29 Thread Peter Maydell
On Sun, 29 Aug 2021 at 17:06, Reinoud Zandijk wrote: > > Hi :) > > Have these patches been applied? How can I easily check it without manually > checking if they are there in a git pullup? Am I notified normally when > patches are applied? Generally when a submaintainer picks up a patchset they'l

applied? Re: [PATCH v1 0/2] Update NVMM support to recent changes, [PATCH v1 1/2] Only check CONFIG_NVMM when NEED_CPU_H is defined, [PATCH v1 2/2] Fix nvmm_ram_block_added() function arguments

2021-08-29 Thread Reinoud Zandijk
Hi :) Have these patches been applied? How can I easily check it without manually checking if they are there in a git pullup? Am I notified normally when patches are applied? With regards, Reinoud On Sun, Jul 18, 2021 at 03:46:48PM +0200, Reinoud Zandijk wrote: > This patchset fixes small NVMM a

[PATCH v1 1/2] Only check CONFIG_NVMM when NEED_CPU_H is defined

2021-07-18 Thread Reinoud Zandijk
Userland targers will otherwise use a poisoned CONFIG_NVMM Signed-off-by: Reinoud Zandijk --- include/sysemu/nvmm.h | 7 --- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/include/sysemu/nvmm.h b/include/sysemu/nvmm.h index 6d216599b0..833670fccb 100644 --- a/include/sysemu/nv