* Implement standard file operation with QEMU
@ 2020-07-16 0:51 casmac
2020-07-16 7:57 ` Philippe Mathieu-Daudé
0 siblings, 1 reply; 4+ messages in thread
From: casmac @ 2020-07-16 0:51 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 2903 bytes --]
Hi all,
I am trying to implment standard file operation (stdio) with QEMU for DSP architecture. The manufacture (TI) provides a runtime library that support posix standard IO, but it left the device level implmentation as hook function calls, like in the library source , it contains add_device() function, and write(),read(),open() are not implemented:
int add_device(char *name,
unsigned flags,
int (*dopen) (const char *path, unsigned flags, int foo),
int (*dclose) (int fno),
int (*dread) (int fno, char *buf, unsigned count),
int (*dwrite) (int fno, const char *buf, unsigned count),
fpos_t (*dlseek) (int fno, fpos_t offset, int origin),
int (*dunlink)(const char *path),
int (*drename)(const char *old_name, const char *new_name))
{
_DEVICE *dt;
strncpy(dt->name,name,8);
dt->name[8] = '\0';
dt->flags = flags;
dt->OPEN = dopen;
dt->CLOSE = dclose;
dt->READ = dread;
dt->WRITE = dwrite;
dt->LSEEK = dlseek;
dt->UNLINK = dunlink;
dt->RENAME = drename;
}
int write(int fildes,
const char *bufptr,
unsigned cnt)
{
/*------------------------------------------------------------------------*/
/* CALL FUNCTION FROM DEVICE TABLE TO PERFORM WRITE FOR THIS DEVICE/FILE */
/*------------------------------------------------------------------------*/
return (*(_stream[fildes]->WRITE)) (fildes,bufptr,cnt);
}
Then, how can we use this runtime library together with QEMu to implement full-stack file oerations? I really appreaciate any advice.
Thanks.
regards,
xiaolei
[-- Attachment #2: Type: text/html, Size: 3143 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Implement standard file operation with QEMU
2020-07-16 0:51 casmac
@ 2020-07-16 7:57 ` Philippe Mathieu-Daudé
0 siblings, 0 replies; 4+ messages in thread
From: Philippe Mathieu-Daudé @ 2020-07-16 7:57 UTC (permalink / raw)
To: casmac, qemu-devel, Alex Bennée, Laurent Vivier,
Marc-André Lureau
Hi Xiaolei,
+Laurent (user-mode)
+Alex (semihosting)
+Marc-André (chardev)
On 7/16/20 2:51 AM, casmac wrote:
> Hi all,
> I am trying to implment standard file operation (stdio) with QEMU for
> DSP architecture. The manufacture (TI) provides a runtime library that
> support posix standard IO, but it left the device level implmentation as
> hook function calls, like in the library source , it contains
> add_device() function, and write(),read(),open() are not implemented:
>
> int add_device(char *name,
> unsigned flags,
> int (*dopen) (const char *path, unsigned flags, int
> foo),
> int (*dclose) (int fno),
> int (*dread) (int fno, char *buf, unsigned count),
> int (*dwrite) (int fno, const char *buf, unsigned
> count),
> fpos_t (*dlseek) (int fno, fpos_t offset, int origin),
> int (*dunlink)(const char *path),
> int (*drename)(const char *old_name, const char
> *new_name))
> {
> _DEVICE *dt;
>
> strncpy(dt->name,name,8);
> dt->name[8] = '\0';
> dt->flags = flags;
> dt->OPEN = dopen;
> dt->CLOSE = dclose;
> dt->READ = dread;
> dt->WRITE = dwrite;
> dt->LSEEK = dlseek;
> dt->UNLINK = dunlink;
> dt->RENAME = drename;
> }
>
> int write(int fildes,
> const char *bufptr,
> unsigned cnt)
> {
>
> /*------------------------------------------------------------------------*/
> /* CALL FUNCTION FROM DEVICE TABLE TO PERFORM WRITE FOR THIS
> DEVICE/FILE */
>
> /*------------------------------------------------------------------------*/
> return (*(_stream[fildes]->WRITE)) (fildes,bufptr,cnt);
> }
>
> Then, how can we use this runtime library together with QEMu to
> implement full-stack file oerations? I really appreaciate any advice.
Trying to understand...
Are you trying to ask "how to implement semihosting for my
qemu-user-tidsp fork"?
Have a look at "hw/semihosting/console.h" and the implementation
(so far only ARM) of qemu_semihosting_console_[in/out].
This might help to plug read/write. Using other stream than
stdin/stdout is not supported (but you can add support) so
open/lseek/close/rename/unlink are not considered.
(for QEMU 'console' is the stdin/stdout subset of stdio).
You can redirect semihosted files with any host chardev,
this is done in qemu_semihosting_connect_chardevs().
You might also have a look at the functions declared in
"hw/semihosting/semihost.h" and how the different TCG helpers
use them.
Regards,
Phil.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Implement standard file operation with QEMU
@ 2020-07-17 15:18 casmac
2020-07-17 15:43 ` Peter Maydell
0 siblings, 1 reply; 4+ messages in thread
From: casmac @ 2020-07-17 15:18 UTC (permalink / raw)
To: Philippe Mathieu-Daudé
Cc: Laurent Vivier, Marc-André Lureau, Alex Bennée,
qemu-devel
[-- Attachment #1: Type: text/plain, Size: 5221 bytes --]
Hello Phil,
What I want to realize is to be able to call standard file operations (open, read, write etc) in the application program, and execute such programs in QEMU. But I am building under system mode.
TI provide copilation toolchain and a library that provide partial functionality from libc. I am hoping to use TI's toolkit to generate object code which contains calls to hook functions, and then use QEMU's host I/O implementation to realize low-level file operation. For example:
_stream[fildes]->WRITE <---hook to ---> qemu_semihosting_console_outs
Are you suggesting that this is done by TCG helpers?
best regards,
xiaolei
------------------ Original ------------------
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>;
Date: Thu, Jul 16, 2020 03:57 PM
To: "casmac"<climber.cui@qq.com>;"qemu-devel"<qemu-devel@nongnu.org>;"Alex Bennée"<alex.bennee@linaro.org>;"Laurent Vivier"<lvivier@redhat.com>;"Marc-André Lureau"<marcandre.lureau@redhat.com>;
Subject: Re: Implement standard file operation with QEMU
Hi Xiaolei,
+Laurent (user-mode)
+Alex (semihosting)
+Marc-André (chardev)
On 7/16/20 2:51 AM, casmac wrote:
> Hi all,
> I am trying to implment standard file operation (stdio) with QEMU for
> DSP architecture. The manufacture (TI) provides a runtime library that
> support posix standard IO, but it left the device level implmentation as
> hook function calls, like in the library source , it contains
> add_device() function, and write(),read(),open() are not implemented:
>
> int add_device(char *name,
> unsigned flags,
> int (*dopen) (const char *path, unsigned flags, int
> foo),
> int (*dclose) (int fno),
> int (*dread) (int fno, char *buf, unsigned count),
> int (*dwrite) (int fno, const char *buf, unsigned
> count),
> fpos_t (*dlseek) (int fno, fpos_t offset, int origin),
> int (*dunlink)(const char *path),
> int (*drename)(const char *old_name, const char
> *new_name))
> {
> _DEVICE *dt;
>
> strncpy(dt->name,name,8);
> dt->name[8] = '\0';
> dt->flags = flags;
> dt->OPEN = dopen;
> dt->CLOSE = dclose;
> dt->READ = dread;
> dt->WRITE = dwrite;
> dt->LSEEK = dlseek;
> dt->UNLINK = dunlink;
> dt->RENAME = drename;
> }
>
> int write(int fildes,
> const char *bufptr,
> unsigned cnt)
> {
>
> /*------------------------------------------------------------------------*/
> /* CALL FUNCTION FROM DEVICE TABLE TO PERFORM WRITE FOR THIS
> DEVICE/FILE */
>
> /*------------------------------------------------------------------------*/
> return (*(_stream[fildes]->WRITE)) (fildes,bufptr,cnt);
> }
>
> Then, how can we use this runtime library together with QEMu to
> implement full-stack file oerations? I really appreaciate any advice.
Trying to understand...
Are you trying to ask "how to implement semihosting for my
qemu-user-tidsp fork"?
Have a look at "hw/semihosting/console.h" and the implementation
(so far only ARM) of qemu_semihosting_console_[in/out].
This might help to plug read/write. Using other stream than
stdin/stdout is not supported (but you can add support) so
open/lseek/close/rename/unlink are not considered.
(for QEMU 'console' is the stdin/stdout subset of stdio).
You can redirect semihosted files with any host chardev,
this is done in qemu_semihosting_connect_chardevs().
You might also have a look at the functions declared in
"hw/semihosting/semihost.h" and how the different TCG helpers
use them.
Regards,
Phil.
[-- Attachment #2: Type: text/html, Size: 5827 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Implement standard file operation with QEMU
2020-07-17 15:18 Implement standard file operation with QEMU casmac
@ 2020-07-17 15:43 ` Peter Maydell
0 siblings, 0 replies; 4+ messages in thread
From: Peter Maydell @ 2020-07-17 15:43 UTC (permalink / raw)
To: casmac
Cc: Laurent Vivier, Marc-André Lureau, Alex Bennée,
Philippe Mathieu-Daudé, qemu-devel
On Fri, 17 Jul 2020 at 16:28, casmac <climber.cui@qq.com> wrote:
> What I want to realize is to be able to call standard file operations (open, read, write etc) in the application program, and execute such programs in QEMU. But I am building under system mode.
> TI provide copilation toolchain and a library that provide partial functionality from libc. I am hoping to use TI's toolkit to generate object code which contains calls to hook functions, and then use QEMU's host I/O implementation to realize low-level file operation. For example:
> _stream[fildes]->WRITE <---hook to ---> qemu_semihosting_console_outs
If the QEMU guest architecture you're using supports
semihosting (eg arm, mips, lm32, m68k, niso2, xtensa), then
you can use it to implement that kind of guest-libc
functionality. What you need to do is entirely in the guest
code: the implementation of the hook function for write
would need to invoke the correct semihosting call.
(For instance on Arm this is "put the arguments into the
correct guest registers/in-memory structures, then invoke
the right SVC instruction".)
If the guest architecture you're using does not have a
semihosting ABI, then you would need to define one, which
is a moderate amount of work and also requires some agreement
about what that ABI definition should look like (eg for
risc-v we asked the risc-v folks to write up a basic
spec document so that everybody implementing semihosting
was working to the same set of requirements).
The other usual way to implement the low-level hook
functions would be for them to talk to emulated devices:
eg a write-to-console function could be implemented to send
the string to a UART device.
thanks
-- PMM
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-07-17 15:44 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-07-17 15:18 Implement standard file operation with QEMU casmac
2020-07-17 15:43 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2020-07-16 0:51 casmac
2020-07-16 7:57 ` Philippe Mathieu-Daudé
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).