Displaying 20 results from an estimated 25 matches for "magicvalue".
2020 Jan 08
2
Position independent code writes absolute pointer
Hello everyone,
I have an issue with some code that I jit/load as position independent code. I have a feeling that it is not possible to solve the issue but I wanted to give it a try.
#include <stdio.h>
int magicValue = 123;
int magicValue2 = 321;
volatile int *pValue = &magicValue;
void printMagicValue()
{
printf("Planschi...\n");
printf("The magic value is %i 0x%p && 0x%p\n", magicValue, &magicValue, pValue);
}
void setMagicValue(int value)
{
magicVa...
2013 Jun 22
2
what should a virtio-mmio transport without a backend look like?
On 21 June 2013 19:45, Christopher Covington <cov at codeaurora.org> wrote:
> You were proposing to use a valid/existing MagicValue/Version/VendorID with a
> special DeviceID that does nothing. I'm saying why not use a valid/existing
> MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0,
> that does nothing?
Ah, I see. Well, it sounds from your quoted mount message as if they
do actually...
2013 Jun 22
2
what should a virtio-mmio transport without a backend look like?
On 21 June 2013 19:45, Christopher Covington <cov at codeaurora.org> wrote:
> You were proposing to use a valid/existing MagicValue/Version/VendorID with a
> special DeviceID that does nothing. I'm saying why not use a valid/existing
> MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0,
> that does nothing?
Ah, I see. Well, it sounds from your quoted mount message as if they
do actually...
2013 Jun 21
3
what should a virtio-mmio transport without a backend look like?
On 21 June 2013 19:01, Christopher Covington <cov at codeaurora.org> wrote:
> Anyhow, I just did a quick experiment with 0-size block devices, and they seem
> to work for me, although trying to mount the device yields the confusing
> message, "mount: mounting /dev/vda on mount failed: Invalid argument".
I'm confused -- what's the significance of zero size
block
2013 Jun 21
3
what should a virtio-mmio transport without a backend look like?
On 21 June 2013 19:01, Christopher Covington <cov at codeaurora.org> wrote:
> Anyhow, I just did a quick experiment with 0-size block devices, and they seem
> to work for me, although trying to mount the device yields the confusing
> message, "mount: mounting /dev/vda on mount failed: Invalid argument".
I'm confused -- what's the significance of zero size
block
2013 Jun 20
3
what should a virtio-mmio transport without a backend look like?
...ckend present.
> (The idea is that QEMU might just always instantiate say 8
> mmio transports, and then whether they actually have a
> blk/net/whatever backend depends on user options).
>
> It looks as if the current linux driver insists (if it sees a
> device tree node) that the MagicValue register at least is
> correct (otherwise it complains). So one possibility would
> be "MagicValue/Version/VendorID must read as usual, DeviceID
> should read as some special "nothing here" value (0?), everything
> else can RAZ/WI".
>
> We could just say "...
2013 Jun 20
3
what should a virtio-mmio transport without a backend look like?
...ckend present.
> (The idea is that QEMU might just always instantiate say 8
> mmio transports, and then whether they actually have a
> blk/net/whatever backend depends on user options).
>
> It looks as if the current linux driver insists (if it sees a
> device tree node) that the MagicValue register at least is
> correct (otherwise it complains). So one possibility would
> be "MagicValue/Version/VendorID must read as usual, DeviceID
> should read as some special "nothing here" value (0?), everything
> else can RAZ/WI".
>
> We could just say "...
2013 Jun 20
0
what should a virtio-mmio transport without a backend look like?
...(The idea is that QEMU might just always instantiate say 8
>> mmio transports, and then whether they actually have a
>> blk/net/whatever backend depends on user options).
>>
>> It looks as if the current linux driver insists (if it sees a
>> device tree node) that the MagicValue register at least is
>> correct (otherwise it complains). So one possibility would
>> be "MagicValue/Version/VendorID must read as usual, DeviceID
>> should read as some special "nothing here" value (0?), everything
>> else can RAZ/WI".
Might it be reaso...
2013 Jun 21
0
what should a virtio-mmio transport without a backend look like?
...to work for me, although trying to mount the device yields the confusing
>> message, "mount: mounting /dev/vda on mount failed: Invalid argument".
>
> I'm confused -- what's the significance of zero size
> block devices?
You were proposing to use a valid/existing MagicValue/Version/VendorID with a
special DeviceID that does nothing. I'm saying why not use a valid/existing
MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0,
that does nothing?
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. i...
2013 Jun 24
0
what should a virtio-mmio transport without a backend look like?
On 06/22/2013 06:51 AM, Peter Maydell wrote:
> On 21 June 2013 19:45, Christopher Covington <cov at codeaurora.org> wrote:
>> You were proposing to use a valid/existing MagicValue/Version/VendorID with a
>> special DeviceID that does nothing. I'm saying why not use a valid/existing
>> MagicValue/Version/VendorID/DeviceID with a special parameter setting, size=0,
>> that does nothing?
[...]
> Also, it's mixing a detail of the backend layer (what...
2013 Oct 22
3
QueuePFN peculiarity in virtio-mmio
...ore importantly: I think that resetting the device (by writing 0
to its status register) should include (ie. *guarantee*) the effects of
setting QueuePFN to zero for all imaginable queues of the device.
This way, a defensive guest that starts up by resetting the device (*)
after identifying it via MagicValue / Version / DeviceID / VendorID
would be able to use the device regardless of the device's prior
QueuePFN setting(s).
(*) Resetting the device is the first step in "2.2.1 Device
Initialization Sequence". It "is not required on initial start up", but
as a guest driver can ne...
2013 Oct 22
3
QueuePFN peculiarity in virtio-mmio
...ore importantly: I think that resetting the device (by writing 0
to its status register) should include (ie. *guarantee*) the effects of
setting QueuePFN to zero for all imaginable queues of the device.
This way, a defensive guest that starts up by resetting the device (*)
after identifying it via MagicValue / Version / DeviceID / VendorID
would be able to use the device regardless of the device's prior
QueuePFN setting(s).
(*) Resetting the device is the first step in "2.2.1 Device
Initialization Sequence". It "is not required on initial start up", but
as a guest driver can ne...
2013 Oct 22
0
QueuePFN peculiarity in virtio-mmio
...that resetting the device (by writing 0
> to its status register) should include (ie. *guarantee*) the effects of
> setting QueuePFN to zero for all imaginable queues of the device.
>
> This way, a defensive guest that starts up by resetting the device (*)
> after identifying it via MagicValue / Version / DeviceID / VendorID
> would be able to use the device regardless of the device's prior
> QueuePFN setting(s).
>
> (*) Resetting the device is the first step in "2.2.1 Device
> Initialization Sequence". It "is not required on initial start up", but...
2015 Jan 20
4
[PATCH v2] virtio-mmio: Update the device to OASIS spec version
..., ARM Ltd.
*
* This module allows virtio devices to be used over a virtual, memory mapped
* platform device.
@@ -50,36 +50,6 @@
*
*
*
- * Registers layout (all 32-bit wide):
- *
- * offset d. name description
- * ------ -- ---------------- -----------------
- *
- * 0x000 R MagicValue Magic value "virt"
- * 0x004 R Version Device version (current max. 1)
- * 0x008 R DeviceID Virtio device ID
- * 0x00c R VendorID Virtio vendor ID
- *
- * 0x010 R HostFeatures Features supported by the host
- * 0x014 W HostFeaturesSel Set of h...
2015 Jan 20
4
[PATCH v2] virtio-mmio: Update the device to OASIS spec version
..., ARM Ltd.
*
* This module allows virtio devices to be used over a virtual, memory mapped
* platform device.
@@ -50,36 +50,6 @@
*
*
*
- * Registers layout (all 32-bit wide):
- *
- * offset d. name description
- * ------ -- ---------------- -----------------
- *
- * 0x000 R MagicValue Magic value "virt"
- * 0x004 R Version Device version (current max. 1)
- * 0x008 R DeviceID Virtio device ID
- * 0x00c R VendorID Virtio vendor ID
- *
- * 0x010 R HostFeatures Features supported by the host
- * 0x014 W HostFeaturesSel Set of h...
2015 Jan 20
1
[PATCH] virtio-mmio: Update the device to OASIS spec version
..., ARM Ltd.
*
* This module allows virtio devices to be used over a virtual, memory mapped
* platform device.
@@ -50,36 +50,6 @@
*
*
*
- * Registers layout (all 32-bit wide):
- *
- * offset d. name description
- * ------ -- ---------------- -----------------
- *
- * 0x000 R MagicValue Magic value "virt"
- * 0x004 R Version Device version (current max. 1)
- * 0x008 R DeviceID Virtio device ID
- * 0x00c R VendorID Virtio vendor ID
- *
- * 0x010 R HostFeatures Features supported by the host
- * 0x014 W HostFeaturesSel Set of h...
2015 Jan 20
1
[PATCH] virtio-mmio: Update the device to OASIS spec version
..., ARM Ltd.
*
* This module allows virtio devices to be used over a virtual, memory mapped
* platform device.
@@ -50,36 +50,6 @@
*
*
*
- * Registers layout (all 32-bit wide):
- *
- * offset d. name description
- * ------ -- ---------------- -----------------
- *
- * 0x000 R MagicValue Magic value "virt"
- * 0x004 R Version Device version (current max. 1)
- * 0x008 R DeviceID Virtio device ID
- * 0x00c R VendorID Virtio vendor ID
- *
- * 0x010 R HostFeatures Features supported by the host
- * 0x014 W HostFeaturesSel Set of h...
2015 Jan 20
0
[PATCH v2] virtio-mmio: Update the device to OASIS spec version
...be used over a virtual, memory mapped
> * platform device.
> @@ -50,36 +50,6 @@
> *
> *
> *
> - * Registers layout (all 32-bit wide):
> - *
> - * offset d. name description
> - * ------ -- ---------------- -----------------
> - *
> - * 0x000 R MagicValue Magic value "virt"
> - * 0x004 R Version Device version (current max. 1)
> - * 0x008 R DeviceID Virtio device ID
> - * 0x00c R VendorID Virtio vendor ID
> - *
> - * 0x010 R HostFeatures Features supported by the host
> - * 0x014...
2015 Jan 20
0
[PATCH v2] virtio-mmio: Update the device to OASIS spec version
...be used over a virtual, memory mapped
> * platform device.
> @@ -50,36 +50,6 @@
> *
> *
> *
> - * Registers layout (all 32-bit wide):
> - *
> - * offset d. name description
> - * ------ -- ---------------- -----------------
> - *
> - * 0x000 R MagicValue Magic value "virt"
> - * 0x004 R Version Device version (current max. 1)
> - * 0x008 R DeviceID Virtio device ID
> - * 0x00c R VendorID Virtio vendor ID
> - *
> - * 0x010 R HostFeatures Features supported by the host
> - * 0x014...
2014 Dec 19
5
[RFC] virtio-mmio: Update the device to OASIS spec version
..., ARM Ltd.
*
* This module allows virtio devices to be used over a virtual, memory mapped
* platform device.
@@ -50,36 +50,6 @@
*
*
*
- * Registers layout (all 32-bit wide):
- *
- * offset d. name description
- * ------ -- ---------------- -----------------
- *
- * 0x000 R MagicValue Magic value "virt"
- * 0x004 R Version Device version (current max. 1)
- * 0x008 R DeviceID Virtio device ID
- * 0x00c R VendorID Virtio vendor ID
- *
- * 0x010 R HostFeatures Features supported by the host
- * 0x014 W HostFeaturesSel Set of h...