From: Gleb Natapov <gleb@redhat.com>
To: qemu-devel@nongnu.org
Cc: kvm@vger.kernel.org, mst@redhat.com, armbru@redhat.com,
blauwirbel@gmail.com, alex.williamson@redhat.com,
kevin@koconnor.net
Subject: [Qemu-devel] [PATCHv5 12/15] Change fw_cfg_add_file() to get full file path as a parameter.
Date: Mon, 15 Nov 2010 16:31:06 +0200 [thread overview]
Message-ID: <1289831469-25540-13-git-send-email-gleb@redhat.com> (raw)
In-Reply-To: <1289831469-25540-1-git-send-email-gleb@redhat.com>
Change fw_cfg_add_file() to get full file path as a parameter instead
of building one internally. Two reasons for that. First caller may need
to know how file is named. Second this moves policy of file naming out
from fw_cfg. Platform may want to use more then two levels of
directories for instance.
Signed-off-by: Gleb Natapov <gleb@redhat.com>
---
hw/fw_cfg.c | 16 ++++------------
hw/fw_cfg.h | 4 ++--
hw/loader.c | 16 ++++++++++++++--
3 files changed, 20 insertions(+), 16 deletions(-)
diff --git a/hw/fw_cfg.c b/hw/fw_cfg.c
index 72866ae..7b9434f 100644
--- a/hw/fw_cfg.c
+++ b/hw/fw_cfg.c
@@ -277,10 +277,9 @@ int fw_cfg_add_callback(FWCfgState *s, uint16_t key, FWCfgCallback callback,
return 1;
}
-int fw_cfg_add_file(FWCfgState *s, const char *dir, const char *filename,
- uint8_t *data, uint32_t len)
+int fw_cfg_add_file(FWCfgState *s, const char *filename, uint8_t *data,
+ uint32_t len)
{
- const char *basename;
int i, index;
if (!s->files) {
@@ -297,15 +296,8 @@ int fw_cfg_add_file(FWCfgState *s, const char *dir, const char *filename,
fw_cfg_add_bytes(s, FW_CFG_FILE_FIRST + index, data, len);
- basename = strrchr(filename, '/');
- if (basename) {
- basename++;
- } else {
- basename = filename;
- }
-
- snprintf(s->files->f[index].name, sizeof(s->files->f[index].name),
- "%s/%s", dir, basename);
+ pstrcpy(s->files->f[index].name, sizeof(s->files->f[index].name),
+ filename);
for (i = 0; i < index; i++) {
if (strcmp(s->files->f[index].name, s->files->f[i].name) == 0) {
FW_CFG_DPRINTF("%s: skip duplicate: %s\n", __FUNCTION__,
diff --git a/hw/fw_cfg.h b/hw/fw_cfg.h
index 4d13a4f..856bf91 100644
--- a/hw/fw_cfg.h
+++ b/hw/fw_cfg.h
@@ -60,8 +60,8 @@ int fw_cfg_add_i32(FWCfgState *s, uint16_t key, uint32_t value);
int fw_cfg_add_i64(FWCfgState *s, uint16_t key, uint64_t value);
int fw_cfg_add_callback(FWCfgState *s, uint16_t key, FWCfgCallback callback,
void *callback_opaque, uint8_t *data, size_t len);
-int fw_cfg_add_file(FWCfgState *s, const char *dir, const char *filename,
- uint8_t *data, uint32_t len);
+int fw_cfg_add_file(FWCfgState *s, const char *filename, uint8_t *data,
+ uint32_t len);
FWCfgState *fw_cfg_init(uint32_t ctl_port, uint32_t data_port,
target_phys_addr_t crl_addr, target_phys_addr_t data_addr);
diff --git a/hw/loader.c b/hw/loader.c
index 49ac1fa..1e98326 100644
--- a/hw/loader.c
+++ b/hw/loader.c
@@ -592,8 +592,20 @@ int rom_add_file(const char *file, const char *fw_dir,
}
close(fd);
rom_insert(rom);
- if (rom->fw_file && fw_cfg)
- fw_cfg_add_file(fw_cfg, rom->fw_dir, rom->fw_file, rom->data, rom->romsize);
+ if (rom->fw_file && fw_cfg) {
+ const char *basename;
+ char fw_file_name[56];
+
+ basename = strrchr(rom->fw_file, '/');
+ if (basename) {
+ basename++;
+ } else {
+ basename = rom->fw_file;
+ }
+ snprintf(fw_file_name, sizeof(fw_file_name), "%s/%s", rom->fw_dir,
+ basename);
+ fw_cfg_add_file(fw_cfg, fw_file_name, rom->data, rom->romsize);
+ }
return 0;
err:
--
1.7.1
next prev parent reply other threads:[~2010-11-15 14:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 14:30 [Qemu-devel] [PATCHv5 00/15] boot order specification Gleb Natapov
2010-11-15 14:30 ` [Qemu-devel] [PATCHv5 01/15] Introduce fw_name field to DeviceInfo structure Gleb Natapov
2010-11-16 8:09 ` Isaku Yamahata
2010-11-16 8:59 ` Gleb Natapov
2010-11-15 14:30 ` [Qemu-devel] [PATCHv5 02/15] Introduce new BusInfo callback get_fw_dev_path Gleb Natapov
2010-11-15 14:30 ` [Qemu-devel] [PATCHv5 03/15] Keep track of ISA ports ISA device is using in qdev Gleb Natapov
2010-11-15 14:30 ` [Qemu-devel] [PATCHv5 04/15] Add get_fw_dev_path callback to ISA bus " Gleb Natapov
2010-11-15 14:30 ` [Qemu-devel] [PATCHv5 05/15] Store IDE bus id in IDEBus structure for easy access Gleb Natapov
2010-11-15 14:31 ` [Qemu-devel] [PATCHv5 06/15] Add get_fw_dev_path callback to IDE bus Gleb Natapov
2010-11-15 14:31 ` [Qemu-devel] [PATCHv5 07/15] Add get_dev_path callback for system bus Gleb Natapov
2010-11-15 14:31 ` [Qemu-devel] [PATCHv5 08/15] Add get_fw_dev_path callback for pci bus Gleb Natapov
2010-11-15 14:31 ` [Qemu-devel] [PATCHv5 09/15] Record which USBDevice USBPort belongs too Gleb Natapov
2010-11-15 14:31 ` [Qemu-devel] [PATCHv5 10/15] Add get_dev_path callback for usb bus Gleb Natapov
2010-11-15 14:31 ` [Qemu-devel] [PATCHv5 11/15] Add bootindex parameter to net/block/fd device Gleb Natapov
2010-11-15 14:31 ` Gleb Natapov [this message]
2010-11-15 14:31 ` [Qemu-devel] [PATCHv5 13/15] Add bootindex for option roms Gleb Natapov
2010-11-15 14:31 ` [Qemu-devel] [PATCHv5 14/15] Add notifier that will be called when machine is fully created Gleb Natapov
2010-11-15 14:31 ` [Qemu-devel] [PATCHv5 15/15] Pass boot device list to firmware Gleb Natapov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1289831469-25540-13-git-send-email-gleb@redhat.com \
--to=gleb@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=armbru@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).