On 7/26/2023 7:54 PM, Sean Christopherson wrote:
> On Wed, Jul 26, 2023, Nikunj A. Dadhania wrote:
>> On 7/24/2023 10:30 PM, Sean Christopherson wrote:
>>>> /proc//smaps
>>>> 7f528be0-7f5c8be0 rw-p 00:01 26629
>&g
Hi Sean,
On 7/24/2023 10:30 PM, Sean Christopherson wrote:
> On Mon, Jul 24, 2023, Nikunj A. Dadhania wrote:
>> On 7/19/2023 5:14 AM, Sean Christopherson wrote:
>>> This is the next iteration of implementing fd-based (instead of vma-based)
>>> memory for KVM gu
On 7/19/2023 5:14 AM, Sean Christopherson wrote:
> This is the next iteration of implementing fd-based (instead of vma-based)
> memory for KVM guests. If you want the full background of why we are doing
> this, please go read the v10 cover letter[1].
>
> The biggest change from v10 is to implemen
David Gibson writes:
> On Tue, Oct 03, 2017 at 08:24:07AM +0200, Cédric Le Goater wrote:
>> On 10/03/2017 05:36 AM, David Gibson wrote:
>> > On Mon, Oct 02, 2017 at 06:27:20PM +0200, Cédric Le Goater wrote:
>> >> On 09/23/2017 10:26 AM, Cédric Le Goater wrote:
>> >>> Hi,
>> >>>
>> >>> Here are a
Hi Michael,
Nikunj A Dadhania writes:
> In some situations, a NUMA guest that supports
> ibm,dynamic-memory-reconfiguration node will end up having flat NUMA
> distances between nodes. This is because of two problems in the
> current code.
>
> 1) Different representations of a
Thomas Huth writes:
> On Mon, 6 Jul 2015 18:02:00 +1000
> Alexey Kardashevskiy wrote:
>
>> On 07/06/2015 05:22 PM, Thomas Huth wrote:
>> > On Mon, 6 Jul 2015 14:09:10 +1000
>> > Alexey Kardashevskiy wrote:
>> >
>> >> This adds a maillist and emails to be used when posting a patch for SLOF.
> .
Dinar valeev writes:
> From: Dinar Valeev
>
> Original issue is home and end keys are not functional in grub2.
> Later I've found other inconsistencies in f1-f12 keys.
>
> "Correct sequence" was crabbed by pressing key on cat running in
> xterm.
>
> Tested with Home, End, F2, Del and F10 keys in
Dinar valeev writes:
> From: Dinar Valeev
>
> Caps behaves like shift only for latin characters.
> In case we're typing - for example with caps enabled, SLOF picks _ char
> from shifted table.
>
> Threat caps as shift only for letters.
>
> Signed-off-by: Dina
Alexey Kardashevskiy writes:
> This adds a maillist and emails to be used when posting a patch for SLOF.
>
> Cc: Benjamin Herrenschmidt
> Cc: Thomas Huth
> Cc: Nikunj A Dadhania
> Signed-off-by: Alexey Kardashevskiy
> ---
>
> I was asked to describe somewhere how
Alexey Kardashevskiy writes:
> On 07/02/2015 09:35 PM, Nikunj A Dadhania wrote:
>> Signed-off-by: Nikunj A Dadhania
>> Reviewed-by: Thomas Huth
>
> If it does not change SLOF behaviour in any way (and it does not,
> right?),
It does not.
> it would be ni
in seek-pos updation code
* Check for Protective MBR Magic
* Check for valid GPT Signature
* Boundary check for allocated block size before reading into the
buffer
Signed-off-by: Nikunj A Dadhania
Reviewed-by: Thomas Huth
---
slof/fs/packages/disk-label.fs | 108
Signed-off-by: Nikunj A Dadhania
Reviewed-by: Thomas Huth
---
slof/fs/little-endian.fs | 6 ++
slof/fs/packages/disk-label.fs | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/slof/fs/little-endian.fs b/slof/fs/little-endian.fs
index f2e4e8d..6b4779e 100644
tection code
* Fixed stack comments
* Rename verify-gpt-partition, as it was doing more than that. Added
comments.
Nikunj A Dadhania (4):
disk-label: simplify gpt-prep-partition? routine
introduce 8-byte LE helpers
disk-label: introduce helper to check fat filesystem
disk-label: add support
Signed-off-by: Nikunj A Dadhania
Reviewed-by: Thomas Huth
---
slof/fs/packages/disk-label.fs | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/slof/fs/packages/disk-label.fs b/slof/fs/packages/disk-label.fs
index b346774..142e54f 100644
--- a/slof/fs/packages
Signed-off-by: Nikunj A Dadhania
Reviewed-by: Thomas Huth
---
slof/fs/packages/disk-label.fs | 41 +++--
1 file changed, 15 insertions(+), 26 deletions(-)
diff --git a/slof/fs/packages/disk-label.fs b/slof/fs/packages/disk-label.fs
index fe1c25e..f1f083a
Segher Boessenkool writes:
> On Thu, Jul 02, 2015 at 11:17:49AM +0530, Nikunj A Dadhania wrote:
>> >> "block" word is not a block number, actually its an allocated host
>> >> address. Rename it to disk-buf along with a associated
>> >> size(dis
Hi Segher,
Segher Boessenkool writes:
> On Tue, Jun 30, 2015 at 04:31:19PM +0530, Nikunj A Dadhania wrote:
>> "block" word is not a block number, actually its an allocated host
>> address. Rename it to disk-buf along with a associated
>> size(disk-buf-size=40
.
Node distance table will not get initialized in certain cases as
ibm,dynamic-reconfiguration-memory path does not initialize the
lookup table.
Call initialize_distance_lookup_table() from drconf path with
appropriate associativity list.
Reported-by: Bharata B Rao
Signed-off-by
Thomas Huth writes:
> Sorry, every time I look at this gpt stuff, my eyes stumble
> over something new ...
No worries :-)
> On Tue, 30 Jun 2015 16:31:21 +0530
> Nikunj A Dadhania wrote:
>
>> For a GPT+LVM combination disk, older bootloader that does not support
>> L
for Protective MBR Magic
* Check for valid GPT Signature
* Boundary check for allocated block size before reading into the
buffer
Signed-off-by: Nikunj A Dadhania
---
slof/fs/packages/disk-label.fs | 99 +-
1 file changed, 79 insertions(+), 20 deletions
Signed-off-by: Nikunj A Dadhania
Reviewed-by: Thomas Huth
---
slof/fs/packages/disk-label.fs | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/slof/fs/packages/disk-label.fs b/slof/fs/packages/disk-label.fs
index e5a0546..347dc5d 100644
--- a/slof/fs/packages
sk-buf and only takes sector number
as argument.
Signed-off-by: Nikunj A Dadhania
Reviewed-by: Thomas Huth
---
slof/fs/packages/disk-label.fs | 78 ++
1 file changed, 41 insertions(+), 37 deletions(-)
diff --git a/slof/fs/packages/disk-label.fs b/slof/f
Signed-off-by: Nikunj A Dadhania
Reviewed-by: Thomas Huth
---
slof/fs/little-endian.fs | 6 ++
slof/fs/packages/disk-label.fs | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/slof/fs/little-endian.fs b/slof/fs/little-endian.fs
index f2e4e8d..6b4779e 100644
Signed-off-by: Nikunj A Dadhania
Reviewed-by: Thomas Huth
---
slof/fs/packages/disk-label.fs | 41 +++--
1 file changed, 15 insertions(+), 26 deletions(-)
diff --git a/slof/fs/packages/disk-label.fs b/slof/fs/packages/disk-label.fs
index fe1c25e..f1f083a
s
* Rename verify-gpt-partition, as it was doing more than that. Added
comments.
Nikunj A Dadhania (5):
disk-label: simplify gpt-prep-partition? routine
introduce 8-byte LE helpers
disk-label: rename confusing "block" word
disk-label: introduce helper to check fat filesystem
dis
Thomas Huth writes:
> On Thu, 25 Jun 2015 12:15:29 +0530
> Nikunj A Dadhania wrote:
>
>> For a GPT+LVM combination disk, older bootloader that does not support
>> LVM, cannot load kernel from LVM.
>>
>> The patch adds support to read from BASIC_DATA UUID parti
Hi Anton/Michael,
Nikunj A Dadhania writes:
> Hi Anton,
>
> Anton Blanchard writes:
>> Hi Nikunj,
>>
>>> From: Nikunj A Dadhania
>>>
>>> powerpc/numa: initialize distance lookup table from drconf path
>>>
>>> In
for Protective MBR Magic
* Check for valid GPT Signature
* Boundary check for allocated block size before reading into the
buffer
Signed-off-by: Nikunj A Dadhania
---
slof/fs/packages/disk-label.fs | 96 +-
1 file changed, 76 insertions(+), 20 deletions
Signed-off-by: Nikunj A Dadhania
---
slof/fs/packages/disk-label.fs | 17 +
1 file changed, 9 insertions(+), 8 deletions(-)
diff --git a/slof/fs/packages/disk-label.fs b/slof/fs/packages/disk-label.fs
index 0995808..7ed5526 100644
--- a/slof/fs/packages/disk-label.fs
+++ b/slof
sk-buf and only takes sector number
as argument.
Signed-off-by: Nikunj A Dadhania
---
slof/fs/packages/disk-label.fs | 78 ++
1 file changed, 41 insertions(+), 37 deletions(-)
diff --git a/slof/fs/packages/disk-label.fs b/slof/fs/packages/disk-label.fs
ind
Signed-off-by: Nikunj A Dadhania
Reviewed-by: Thomas Huth
---
slof/fs/little-endian.fs | 6 ++
slof/fs/packages/disk-label.fs | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/slof/fs/little-endian.fs b/slof/fs/little-endian.fs
index f2e4e8d..6b4779e 100644
patch 4: As we need to detect FAT partition, implement a helper that
can be used both from GPT code and "fat-bootblock?"
patch 5: Implement GPT FAT for LVM suport and make GPT detection code
robust
Nikunj A Dadhania (5):
disk-label: simplify gpt-prep-partitio
Signed-off-by: Nikunj A Dadhania
Reviewed-by: Thomas Huth
---
slof/fs/packages/disk-label.fs | 42 --
1 file changed, 16 insertions(+), 26 deletions(-)
diff --git a/slof/fs/packages/disk-label.fs b/slof/fs/packages/disk-label.fs
index fe1c25e..bb64d57
Thomas Huth writes:
> On Mon, 22 Jun 2015 13:29:47 +0530
> Nikunj A Dadhania wrote:
>
>> * Check for Protective MBR Magic
>> * Check for valid GPT Signature
>> * Boundary check for allocated block size before reading into the
>> buffer
>>
>> Sign
Thomas Huth writes:
> On Mon, 22 Jun 2015 13:29:46 +0530
> Nikunj A Dadhania wrote:
>
>> For a GPT+LVM combination disk, older bootloader that does not support
>> LVM, cannot load kernel from LVM.
>>
>> The patch add support to read from BASIC_DATA UUID
>
Segher Boessenkool writes:
> On Tue, Jun 23, 2015 at 09:34:44AM +0200, Thomas Huth wrote:
>> > +: load-from-gpt-partition ( [ addr ] -- size | TRUE )
>>
>> What do you mean with addr in square brackets? Is it optional?
>
> And "size | TRUE"? The code even returns "false" instead, which
> usuall
Hi Anton,
Anton Blanchard writes:
> Hi Nikunj,
>
>> From: Nikunj A Dadhania
>>
>> powerpc/numa: initialize distance lookup table from drconf path
>>
>> In some situations, a NUMA guest that supports
>> ibm,dynamic-memory-reconfiguration node will en
Hi Segher,
Segher Boessenkool writes:
> On Mon, Jun 22, 2015 at 01:29:45PM +0530, Nikunj A Dadhania wrote:
>> +: has-fat-filesystem ( block -- true | false )
>> + \ block 0 byte 0-2 is a jump instruction in all FAT
>> + \ filesystems.
>
> "block" the
* Check for Protective MBR Magic
* Check for valid GPT Signature
* Boundary check for allocated block size before reading into the
buffer
Signed-off-by: Nikunj A Dadhania
---
slof/fs/packages/disk-label.fs | 21 +
1 file changed, 17 insertions(+), 4 deletions(-)
diff
Signed-off-by: Nikunj A Dadhania
---
slof/fs/packages/disk-label.fs | 22 +-
1 file changed, 13 insertions(+), 9 deletions(-)
diff --git a/slof/fs/packages/disk-label.fs b/slof/fs/packages/disk-label.fs
index 2cf1b85..e317e93 100644
--- a/slof/fs/packages/disk-label.fs
+++ b
can be used both from GPT code and "try-dos-files"
patch 4: Implement GPT FAT for LVM suport.
patch 5: Make GPT detection code robust
Nikunj A Dadhania (5):
disk-label: simplify gpt-prep-partition? routine
introduce 8-byte LE helpers
disk-label: introduce helper to
Signed-off-by: Nikunj A Dadhania
---
slof/fs/packages/disk-label.fs | 36 +---
1 file changed, 13 insertions(+), 23 deletions(-)
diff --git a/slof/fs/packages/disk-label.fs b/slof/fs/packages/disk-label.fs
index fe1c25e..2305eee 100644
--- a/slof/fs/packages/disk
For a GPT+LVM combination disk, older bootloader that does not support
LVM, cannot load kernel from LVM.
The patch add support to read from BASIC_DATA UUID
partition. Installer has installed CHRP-BOOT config on a FAT file
system.
Signed-off-by: Nikunj A Dadhania
---
slof/fs/packages/disk
Signed-off-by: Nikunj A Dadhania
---
slof/fs/little-endian.fs | 6 ++
slof/fs/packages/disk-label.fs | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/slof/fs/little-endian.fs b/slof/fs/little-endian.fs
index f2e4e8d..6b4779e 100644
--- a/slof/fs/little-endian.fs
Thomas Huth writes:
> On Wed, 17 Jun 2015 17:34:13 +0530
> Nikunj A Dadhania wrote:
>
>> Nikunj A Dadhania writes:
>>
>> > Thomas Huth writes:
>> >>> +\ Check for GPT MSFT BASIC DATA GUID - vfat based
>> >>> +EBD0A0A2 CONSTANT
Thomas Huth writes:
> On Thu, 11 Jun 2015 15:48:49 +0530
> Nikunj A Dadhania wrote:
>
>> + block-size * to seek-pos
>> + block gpt>part-entry-size l@-le to gpt-part-size
>> + block gpt>num-part-entry l@-le dup 0= IF FALSE EXIT THEN
>> +
Nikunj A Dadhania writes:
> Thomas Huth writes:
>>> +\ Check for GPT MSFT BASIC DATA GUID - vfat based
>>> +EBD0A0A2 CONSTANT GPT-BASIC-DATA-PARTITION-1
>>> +B9E5 CONSTANT GPT-BASIC-DATA-PARTITION-2
>>> +4433 CONSTANT GPT-BASIC-DATA-PAR
Thomas Huth writes:
> On Thu, 11 Jun 2015 15:48:49 +0530
> Nikunj A Dadhania wrote:
>
>> For a GPT+LVM combination disk, older bootloader that does not support
>> LVM, cannot load kernel from LVM.
>>
>> The patch add support to read from BASIC_DATA UUID
>
Nikunj A Dadhania writes:
> Reworded commit log:
>
> From: Nikunj A Dadhania
>
> powerpc/numa: initialize distance lookup table from drconf path
>
Ping ?
Regards
Nikunj
___
Linuxppc-dev mailing list
Linuxppc-dev@list
For a GPT+LVM combination disk, older bootloader that does not support
LVM, cannot load kernel from LVM.
The patch add support to read from BASIC_DATA UUID
partition. Installer has installed CHRP-BOOT config on a FAT file
system.
Signed-off-by: Nikunj A Dadhania
---
slof/fs/packages/disk
Reworded commit log:
From: Nikunj A Dadhania
powerpc/numa: initialize distance lookup table from drconf path
In some situations, a NUMA guest that supports
ibm,dynamic-memory-reconfiguration node will end up having flat NUMA
distances between nodes. This is because of two problems in the
er to skip the length field before
sending the associativity list.
Call initialize_distance_lookup_table() from drconf path with
appropriate associativity list.
Reported-by: Bharata B Rao
Signed-off-by: Nikunj A Dadhania
---
arch/powerpc/mm/numa.c | 16 +---
1 file changed, 13
Dinar Valeev writes:
> On Tue, Jun 2, 2015 at 11:47 AM, Nikunj A Dadhania
> wrote:
>> Dinar valeev writes:
>>> @@ -262,7 +258,7 @@ static void check_key_code(uint8_t *buf)
>>> case 0x43:
>>>
Dinar valeev writes:
> From: Dinar Valeev
>
> Original issue is home and end keys are not functional in grub2.
> Later I've found other inconsistencies in f1-f12 keys.
>
> "Correct sequence" was crabbed by pressing key on cat running in
> xterm.
>
> Tested with Home, End, F2, Del and F10 keys in
nes that Thomas pointed:
Reviewed-by: Nikunj A Dadhania
> ---
> board-js2x/slof/helper.fs |5 +
> board-qemu/slof/helper.fs |4
> board-qemu/slof/pci-device_1234_.fs | 10 +-
> slof/fs/fbuffer.fs |
qemu: faster hv-logical-memop based
>
> With standard graphical settings on board-qemu, we go from 512 hcall
> invocations per character down to 16.
>
> Suggested-by: Thomas Huth
> Signed-off-by: Greg Kurz
Reviewed-by: Nikunj A Dadhania
> ---
> board-js2x/slof/helper.fs
address by itself and drop the confusing
> "char-width screen-depth * -" address adjustment.
Much better :-)
Reviewed-by: Nikunj A Dadhania
>
> Signed-off-by: Greg Kurz
> ---
> slof/fs/fbuffer.fs |4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Greg Kurz writes:
> On Wed, 27 May 2015 10:41:06 +0530
> Nikunj A Dadhania wrote:
>
>> Greg Kurz writes:
>>
>> > SLOF currently calls hv-logical-load and hv-logical-store for every pixel
>> > when enabling or disabling the cursor. This is suboptimal when
Greg Kurz writes:
> SLOF currently calls hv-logical-load and hv-logical-store for every pixel
> when enabling or disabling the cursor. This is suboptimal when writing one
> char at a time to the console since terminal-write always toggles the cursor.
> And this is precisely what grub is doing whe
Alexey Kardashevskiy writes:
> On 04/27/2015 06:02 PM, Nikunj A Dadhania wrote:
>> patch 1: Fixes a bug in pci-to-pci bridge while programming the limit
>> registers during probe
>> patch 2,3: Support 64-bit address translation and usb devices can have
>>
Thomas Huth writes:
> On Mon, 27 Apr 2015 13:32:33 +0530
> Nikunj A Dadhania wrote:
>
>> PCI Enumeration has been part of SLOF. Now with hotplug code addition
>> in QEMU, it makes more sense to have this code in one place,
>> i.e. QEMU.
>>
>> Adding ro
the devices.
Signed-off-by: Nikunj A Dadhania
---
board-qemu/slof/pci-phb.fs | 44 +++-
slof/fs/pci-properties.fs | 6 +-
2 files changed, 48 insertions(+), 2 deletions(-)
diff --git a/board-qemu/slof/pci-phb.fs b/board-qemu/slof/pci-phb.fs
index
-by: Nikunj A Dadhania
---
slof/fs/devices/pci-class_0c.fs | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/slof/fs/devices/pci-class_0c.fs b/slof/fs/devices/pci-class_0c.fs
index 9c47325..39453fb 100644
--- a/slof/fs/devices/pci-class_0c.fs
+++ b/slof/fs/devices/pci
Signed-off-by: Nikunj A Dadhania
---
slof/fs/translate.fs | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/slof/fs/translate.fs b/slof/fs/translate.fs
index e2633e5..9654f24 100644
--- a/slof/fs/translate.fs
+++ b/slof/fs/translate.fs
@@ -33,11 +33,9 @@
dup l@ FF
patch 1: Fixes a bug in pci-to-pci bridge while programming the limit
registers during probe
patch 2,3: Support 64-bit address translation and usb devices can have
64-bit pci memory BARs
patch 4: Use QEMU create device tree nodes and program the BARs
Nikunj A Dadhania
of the bug 0x got programmed in the memory
limit register. All the mmio reads across the pci-to-pci bridge
started failing during probe.
All pci-bridge-set-[mmio,mem,io]-base sufferred from similar problem.
Suggested-by: Thomas Huth
Signed-off-by: Nikunj A Dadhania
---
slof/fs/pci-scan.fs
Thomas Huth writes:
> On Fri, 24 Apr 2015 12:56:57 +0200
> Thomas Huth wrote:
>
>> On Fri, 24 Apr 2015 09:22:33 +0530
>> Nikunj A Dadhania wrote:
>>
>> >
>> > Hi Thomas,
>> >
>> > Thomas Huth writes:
>> &g
Thomas Huth writes:
> On Fri, 24 Apr 2015 12:56:57 +0200
> Thomas Huth wrote:
>
>> On Fri, 24 Apr 2015 09:22:33 +0530
>> Nikunj A Dadhania wrote:
>>
>> >
>> > Hi Thomas,
>> >
>> > Thomas Huth writes:
>> &g
Thomas Huth writes:
> On Fri, 24 Apr 2015 09:22:33 +0530
> Nikunj A Dadhania wrote:
>
>>
>> Hi Thomas,
>>
>> Thomas Huth writes:
>> > Am Wed, 22 Apr 2015 16:27:19 +0530
>> > schrieb Nikunj A Dadhania :
>> >
>> >> With
Hi Thomas,
Thomas Huth writes:
> Hi Nikunj,
>
> On Wed, 22 Apr 2015 16:27:20 +0530
> Nikunj A Dadhania wrote:
>
>> PCI Enumeration has been part of SLOF. Now with hotplug code addition
>> in Qemu, it makes more sense to have this code a one place, i.e. Qemu.
>
&
Hi Thomas,
Thomas Huth writes:
> Am Wed, 22 Apr 2015 16:27:19 +0530
> schrieb Nikunj A Dadhania :
>
>> With the addition of 64-bit BARS and increase in the mmio address
>> space, the code was hitting this limit. The memory of pci devices
>> across the bridges were
With the addition of 64-bit BARS and increase in the mmio address
space, the code was hitting this limit. The memory of pci devices
across the bridges were not accessible due to which the drivers
failed.
Signed-off-by: Nikunj A Dadhania
---
board-qemu/slof/pci-phb.fs | 3 ++-
1 file changed, 2
devices.
Signed-off-by: Nikunj A Dadhania
---
board-qemu/slof/pci-phb.fs | 44 +++-
slof/fs/pci-properties.fs | 6 +-
2 files changed, 48 insertions(+), 2 deletions(-)
diff --git a/board-qemu/slof/pci-phb.fs b/board-qemu/slof/pci-phb.fs
index e307d95
size.
> At the moment rings are quite small (256) and allocated with
> 4096 alignment, this is why we have not been having issues with
> this so far.
>
> Signed-off-by: Alexey Kardashevskiy
Reviewed-by: Nikunj A Dadhania
> ---
> Changes:
> v2:
> * remove magic n
Alexey Kardashevskiy writes:
> The value returned by virtio_vring_size() is used to allocate memory
> for vring. The used descriptor list (array of vring_used_elem) is
> counted by the header - vring_used struct - is not.
>
> This fixes virtio_vring_size() to return the correct size.
> At the mom
[i].desc =
> SLOF_alloc_mem_aligned(virtio_vring_size(vq[i].size), 4096);
> slof/helpers.c|70| void *SLOF_alloc_mem_aligned(long size, long align)
>
> Signed-off-by: Alexey Kardashevskiy
Reviewed-by: Nikunj A Dadhania
> ---
> include/helpers.h | 2 +-
> slof/helpers.c| 2 +-
>
Thomas Huth writes:
> On Wed, 11 Mar 2015 17:26:32 +1100
> Alexey Kardashevskiy wrote:
>
>> At the moment SLOF adds a "device_type" property automatically for
>> every single PCI device based on its class even if there is no SLOF
>> driver for such a device. OF1275 says that "device_type" is for
exception and hence needs to know the updated RTAS.
>
> Enhancements to qemu to handle the private HCALL, prepare
> error log and invoke machine check notification routine
> are in a separate patch.
>
> Signed-off-by: Nikunj A. Dadhania
> Signed-off-by: Aravinda Prasad
Than
Alexey Kardashevskiy writes:
> PCI spec says that lower 20 bits are assumed 0xF. The existing code
> seems to get it right in pci-bridge-set-mem-limit.
>
> However pci-bridge-set-mem-base does not account 0xF and poison
> the limit. Since the limit is not stored anywhere in SLOF and only
Alexey Kardashevskiy writes:
> The previous scheme always put 0 as a parent slot#. However it is
> not always the case and QEMU's PCI bridge does not support putting
> device at slot#0 as it claims SHPC support for hotplug.
>
> This modifies the interrups map to let the linux guest resolve XICS
>
Alexey Kardashevskiy writes:
> The previous scheme always put 0 as a parent slot#. However it is
> not always the case and QEMU's PCI bridge does not support putting
> device at slot#0 as it claims SHPC support for hotplug.
>
> This modifies the interrups map to let the linux guest resolve XICS
>
81 matches
Mail list logo
