g to learn theconcepts of how a board is
brought up in general along with some ARMv8 concepts.
Thanks and Regards
Sanjeev
Adapter associated to QEMU?
Thanks & Regards,
Sanjeev.
Hi,
I am starting QEMU as below.
qemu-system-aarch64 [] -device ivshmem-plain,memdev=hostmem -object
memory-backend-file,size=1M,share=on,mem-path=/dev/shm/ivshmem,id=hostmem
before this, i am starting ivshmem-server which i build from QEMU source
git repo. i am able to see ivshmem device crea
-device
virtio-net-device,netdev=mynet0,mac=52:55:00:d1:55:01 -device
virtio-rng-device -device ivshmem-plain,memdev=hostmem -object
memory-backend-file,size=1M,share=on,mem-path=/dev/shm/ivshmem,id=hostmem
-nographic
Thanks & Regards,
Sanjeev.
On Tue, Mar 19, 2024 at 3:58 PM Peter Maydell
w
shared with you
with the supported board that supports PCI bus ?
On Wed, Mar 20, 2024 at 3:21 PM Peter Maydell
wrote:
> On Wed, 20 Mar 2024 at 06:40, Sanjeev Kumar
> wrote:
> >
> > Hi,
> > Sorry for incomplete command.
> > here is the complete command line.
>
Hi,
our kernel is build with aarch64le. it is 64 bit ARM architecture.
when i am trying to use virt as machine, then qemu isn't starting. it is
being stuck after entering command,
On Wed, Mar 20, 2024 at 7:06 PM Peter Maydell
wrote:
> On Wed, 20 Mar 2024 at 13:06, Sanjeev Kumar
cpu we are using cortex-a57 because it is nearby to our actual hardware
exynos v9
On Thu, Mar 21, 2024 at 1:46 PM Sanjeev Kumar
wrote:
> Hi,
> our kernel is build with aarch64le. it is 64 bit ARM architecture.
> when i am trying to use virt as machine, then qemu isn't starting.
as we are beginners. can you please guide us on using virt cpu please.
On Thu, Mar 21, 2024 at 1:52 PM Sanjeev Kumar
wrote:
> cpu we are using cortex-a57 because it is nearby to our actual hardware
> exynos v9
>
> On Thu, Mar 21, 2024 at 1:46 PM Sanjeev Kumar
> wrote:
>
>&
Hi,
is there any other mechanism of shared memory with QEMU other than ivshmem?
I tried ivshmem with ubuntu vm with qemu x86_64 and it is working fine. but
our use case is with ARM and ivshmem isn't supported by our custom VM. so
please let me know if we have any other mechanism other than ivshmem.
and forgot to mention. why our VM doesn't support ivshmem because it
doesn't have PCI supported.
Is there any other shared memory mechanism QEMU which doesn't use the PCI
interface?
On Tue, May 14, 2024 at 11:28 AM Sanjeev Kumar
wrote:
> Hi,
> is there any other mechanism
us BAR
and i was able to get data.
similarly can you please help me with ivshmem-flat like where is the
location to write/read the data from host and in guest.
Thanks & Regards,
Sanjeev.
On Tue, May 14, 2024 at 9:56 PM Philippe Mathieu-Daudé
wrote:
> On 14/5/24 12:23, Sanjeev Kumar wrot
g/
patches.
without that prop,
-chardev socket,path=/tmp/ivshmem_socket,id=ivshmem_flat -device
ivshmem-flat,chardev=ivshmem_flat,x-irq-qompath='/machine/unattached/device[4]/gic/unnamed-gpio-in[0]',x-bus-qompath='/sysbus'
isn't working.
On Thu, May 16, 2024 at 2:52 PM S
use them, it is throwing error of
property is missing
x-bus-qompath
Please check and let me know which is correct patchset to use.
Thanks & Regards
On Thu, 16 May 2024 at 3:59 PM, Gustavo Romero
wrote:
> Hi Sanjeev,
>
> On 5/16/24 11:22 AM, Sanjeev Kumar wrote:
> > Hi Philipp
)
x-bus-address-shmem = 1074790400 (0x4010)
mmio 400ff000/0010
mmio 4010/0040
now need to explore in guest os(QNX) on how to read this memory location.
On Thu, May 16, 2024 at 11:35 PM Sanjeev Kumar
wrote:
> Hi Gustavo,
> Thanks
o
wrote:
> Hi Sanjeev,
>
> On 5/17/24 3:02 PM, Sanjeev Kumar wrote:
> > Hi Gustavo,
> > I understood difference between the two patchsets. thanks for the
> ivshmem-flat. i will try to get info from QNX side how to access the memory
> location in QNX. with the ivshmem-flat
se graphics framerate.
Thanks & Regards,
Sanjeev.
l 2024 at 12:33, Sanjeev Kumar wrote:
>>
>> Hi,
>> I am trying to passthrough GPU to qemu-system-aarch64le. why i need to do
>> this is, the graphics running in OS hosted on qemu-system-aarch64le is very
>> less framerate. As there is no PCI support, when i add &quo
17 matches
Mail list logo